From: Andrew Morton <akpm@osdl.org>
To: Jes Sorensen <jes@sgi.com>
Cc: stern@rowland.harvard.edu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/8] Notifier chain update: API changes
Date: Thu, 16 Feb 2006 12:18:31 -0800 [thread overview]
Message-ID: <20060216121831.6904376c.akpm@osdl.org> (raw)
In-Reply-To: <yq0u0azxwwg.fsf@jaguar.mkp.net>
Jes Sorensen <jes@sgi.com> wrote:
>
> >>>>> "Alan" == Alan Stern <stern@rowland.harvard.edu> writes:
>
> Alan> The kernel's implementation of notifier chains is unsafe. There
> Alan> is no protection against entries being added to or removed from
> Alan> a chain while the chain is in use. The issues were discussed in
> Alan> this thread:
>
> Alan> http://marc.theaimsgroup.com/?l=linux-kernel&m=113018709002036&w=2
>
> Hi,
>
> I was wondering if there was anything blocking this change from going
> in? I'd quite like to see it as it would avoid me from inventing yet
> another notifier chain implementation ;-)
>
It's still lurking in my to-apply folder - will get onto it soon.
next prev parent reply other threads:[~2006-02-16 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 16:03 Alan Stern
2006-02-16 13:20 ` Jes Sorensen
2006-02-16 20:18 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-18 21:42 Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060216121831.6904376c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®