From: Peter Hurley <peter@hurleysoftware.com>
To: paulmck@linux.vnet.ibm.com
Cc: Pranith Kumar <bobby.prani@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Huang Ying <ying.huang@intel.com>,
linux-kernel@vger.kernel.org, David Howells <dhowells@redhat.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] llist: Fix missing lockless_dereference()
Date: Tue, 10 Feb 2015 12:29:24 -0500 [thread overview]
Message-ID: <54DA3FF4.3010700@hurleysoftware.com> (raw)
In-Reply-To: <20150210163810.GP4166@linux.vnet.ibm.com>
On 02/10/2015 11:38 AM, Paul E. McKenney wrote:
> On Tue, Feb 10, 2015 at 09:03:50AM -0500, Peter Hurley wrote:
>> On 02/06/2015 09:08 PM, Mathieu Desnoyers wrote:
>>> A lockless_dereference() appears to be missing in llist_del_first().
>>> It should only matter for Alpha in practice.
>>>
>>> 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>
>>> CC: Pranith Kumar <bobby.prani@gmail.com>
>>> CC: stable@vger.kernel.org # v3.1+
>>> ---
>>> lib/llist.c | 8 +++++++-
>>> 1 file changed, 7 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/lib/llist.c b/lib/llist.c
>>> index f76196d..f34e176 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 <linux/rcupdate.h>
>>
>> Pranith,
>>
>> I didn't realize you put lockless_dereference() in rcupdate.h
>>
>> If the point of lockless_reference() is to provide a utility function for
>> situations _not_ involving RCU, then it doesn't make sense to provide it
>> in an RCU header file.
>
> OK, I'll bite. Just where do you suggest putting it? ;-)
Two possibilities:
1. linux/compiler.h where READ/WRITE/ACCESS_ONCE() are, or
2. a new arch-independent header sucked in by asm/barrier.h (because it's
basically a barrier abstraction, in the same way that smp_load_acquire/
smp_store_release are)
> That question aside, lockless_dereference() does resemble the
> rcu_dereference() family of APIs. This of course means that having it in
> rcupdate.h near rcu_dereference() makes it easier to maintain, given that
> needed changes to one are likely to require at least review of the rest.
I can understand how and why it got there.
But it's not an RCU abstraction, so having random users pulling in RCU headers
to get at a convenient (but not strictly necessary) helper function is less than
ideal.
Honestly, I'd rather see the naked smp_read_barrier_depends() than wondering why
someone grabbed linux/rcupdate.h for the lockless list implementation.
Regards,
Peter Hurley
>>> /**
>>> @@ -67,7 +68,12 @@ struct llist_node *llist_del_first(struct llist_head *head)
>>> {
>>> struct llist_node *entry, *old_entry, *next;
>>>
>>> - entry = head->first;
>>> + /*
>>> + * 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.
>>> + */
>>> + entry = lockless_dereference(head->first);
>>> for (;;) {
>>> if (entry == NULL)
>>> return NULL;
>>>
>>
>
next prev parent reply other threads:[~2015-02-10 17:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 2:08 [PATCH] llist: Fix missing lockless_dereference() Mathieu Desnoyers
2015-02-07 22:16 ` Greg KH
2015-02-07 22:30 ` Mathieu Desnoyers
2015-02-08 0:18 ` Matt Turner
2015-02-08 0:29 ` Greg KH
2015-02-08 0:47 ` Michael Cree
2015-02-08 0:59 ` Greg KH
2015-02-08 1:12 ` Michael Cree
2015-02-08 1:20 ` Greg KH
2015-02-08 4:25 ` Mathieu Desnoyers
2015-02-10 1:52 ` Huang Ying
2015-02-10 3:42 ` Mathieu Desnoyers
2015-02-10 9:30 ` Michael Cree
2015-02-08 0:09 ` Paul E. McKenney
2015-02-10 14:03 ` Peter Hurley
2015-02-10 16:38 ` Paul E. McKenney
2015-02-10 17:29 ` Peter Hurley [this message]
2015-02-10 18:03 ` Paul E. McKenney
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=54DA3FF4.3010700@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=stable@vger.kernel.org \
--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.