From: Dipankar Sarma <dipankar@in.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Allow lockless traversal of notifier lists
Date: Tue, 29 Nov 2005 11:41:06 +0530 [thread overview]
Message-ID: <20051129061106.GD4359@in.ibm.com> (raw)
In-Reply-To: <20051129000158.GE7209@brahms.suse.de>
On Tue, Nov 29, 2005 at 01:01:58AM +0100, Andi Kleen wrote:
> On Mon, Nov 28, 2005 at 11:12:03PM +0530, Dipankar Sarma wrote:
>
> Ok third version, hopefully Dipankar proof now.
>
Not quite. I spoke without looking at the code of the whole
notifier_call_chain() function.
> + * against parallel traversals.
> *
> * Returns zero on success, or %-ENOENT on failure.
> */
> @@ -171,10 +177,12 @@
> int notifier_call_chain(struct notifier_block **n, unsigned long val, void *v)
> {
> int ret=NOTIFY_DONE;
> - struct notifier_block *nb = *n;
> -
> + struct notifier_block *nb;
> + smp_read_barrier_depends();
> + nb = *n;
> while(nb)
> {
> + smp_read_barrier_depends();
> ret=nb->notifier_call(nb,val,v);
> if(ret&NOTIFY_STOP_MASK)
> {
Looking at the full code, it seems to me that we dereference
the first notifier block only inside the while(nb) loop.
That means the smp_read_barrier_depends() in the while(nb)
loop should be sufficient - IOW, the previous version of
the patch with one smp_read_barrier_depends() was good.
Sorry about the confusion.
Thanks
Dipankar
prev parent reply other threads:[~2005-11-29 6:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 13:37 [PATCH] Allow lockless traversal of notifier lists Andi Kleen
2005-11-28 16:01 ` Dipankar Sarma
2005-11-28 16:05 ` Andi Kleen
2005-11-28 16:17 ` Dipankar Sarma
2005-11-28 16:27 ` Andi Kleen
2005-11-28 17:42 ` Dipankar Sarma
2005-11-29 0:01 ` Andi Kleen
2005-11-29 6:11 ` Dipankar Sarma [this message]
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=20051129061106.GD4359@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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