From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Pranith Kumar <bobby.prani@gmail.com>
Cc: Huang Ying <ying.huang@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
David Howells <dhowells@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] llist: Fix missing memory barrier
Date: Fri, 6 Feb 2015 14:12:32 +0000 (UTC) [thread overview]
Message-ID: <625236311.87350.1423231952716.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <CAJhHMCDDG2Woiv1E3OnPCWv33k7+1FVRbmmc5EN3Gxim3zoJsA@mail.gmail.com>
----- Original Message -----
> From: "Pranith Kumar" <bobby.prani@gmail.com>
> To: "Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>
> Cc: "Huang Ying" <ying.huang@intel.com>, "LKML" <linux-kernel@vger.kernel.org>, "Paul McKenney"
> <paulmck@linux.vnet.ibm.com>, "David Howells" <dhowells@redhat.com>
> Sent: Thursday, February 5, 2015 10:44:07 PM
> Subject: Re: [PATCH] llist: Fix missing memory barrier
>
> Hi Mathieu,
>
> On Thu, Feb 5, 2015 at 10:06 PM, Mathieu Desnoyers
> <mathieu.desnoyers@efficios.com> wrote:
> > A smp_read_barrier_depends() appears to be missing in llist_del_first().
> > It should only matter for Alpha in practice. Adding it after the check
> > of entry against NULL allows skipping the barrier in a common case.
>
> We recently decided on using lockless_dereference() instead of
> hard-coding smp_read_barrier_depends()[1]. The advantage is that
> lockless_dereference() clearly shows what loads are being ordered.
> Could you resend the patch using that API?
Since llist.h has been introduced prior to 3.18, I'm wondering if
it would be worthwhile to submit 2 patches for the purpose of
backporting to stable branches:
1) Fix introducing smp_read_barrier_depends() (for master and
stable branches)
2) Move master from smp_read_barrier_depends() to
lockless_dereference(),
Thoughts ?
Thanks!
Mathieu
>
> Thanks!
>
> [1] http://lkml.iu.edu/hypermail/linux/kernel/1410.3/04561.html
>
> >
> > Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> > CC: Huang Ying <ying.huang@intel.com>
> > CC: Paul McKenney <paulmck@linux.vnet.ibm.com>
> > CC: David Howells <dhowells@redhat.com>
> > ---
> > lib/llist.c | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/lib/llist.c b/lib/llist.c
> > index f76196d..72861f3 100644
> > --- a/lib/llist.c
> > +++ b/lib/llist.c
> > @@ -26,6 +26,7 @@
> > #include <linux/export.h>
> > #include <linux/interrupt.h>
> > #include <linux/llist.h>
> > +#include <asm/barrier.h>
> >
> >
> > /**
> > @@ -72,6 +73,12 @@ struct llist_node *llist_del_first(struct llist_head
> > *head)
> > if (entry == NULL)
> > return NULL;
> > old_entry = entry;
> > + /*
> > + * Load entry before entry->next. Matches the implicit
> > + * memory barrier before the cmpxchg in llist_add_batch(),
> > + * which ensures entry->next is stored before entry.
> > + */
> > + smp_read_barrier_depends();
> > next = entry->next;
> > entry = cmpxchg(&head->first, old_entry, next);
> > if (entry == old_entry)
> > --
> > 2.1.4
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
>
>
> --
> Pranith
>
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2015-02-06 14:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 3:06 [PATCH] llist: Fix missing memory barrier Mathieu Desnoyers
2015-02-06 3:44 ` Pranith Kumar
2015-02-06 14:12 ` Mathieu Desnoyers [this message]
2015-02-06 15:03 ` Greg Kroah-Hartman
2015-02-06 22:16 ` Mathieu Desnoyers
2015-02-06 22:42 ` Greg Kroah-Hartman
2015-02-06 15:17 ` Peter Hurley
2015-02-06 22:18 ` Mathieu Desnoyers
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=625236311.87350.1423231952716.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=ying.huang@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.