From: Roman Gushchin <klamm@yandex-team.ru>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
paulmck@linux.vnet.ibm.com,
Jesper Dangaard Brouer <brouer@redhat.com>,
Dipankar Sarma <dipankar@in.ibm.com>,
zhmurov@yandex-team.ru, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
James Morris <jmorris@namei.org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Patrick McHardy <kaber@trash.net>,
David Laight <David.Laight@ACULAB.COM>
Subject: Re: [PATCH v2] rcu: fix a race in hlist_nulls_for_each_entry_rcu macro
Date: Thu, 30 May 2013 12:25:24 +0400 [thread overview]
Message-ID: <51A70CF4.1020807@yandex-team.ru> (raw)
In-Reply-To: <1369854387.5109.77.camel@edumazet-glaptop>
On 29.05.2013 23:06, Eric Dumazet wrote:
> On Wed, 2013-05-29 at 14:09 +0400, Roman Gushchin wrote:
>
> True, these lookup functions are usually structured the same around the
> hlist_nulls_for_each_entry_rcu() loop.
>
> A barrier() right before the loop seems to be a benefit, the size of
> assembly code is reduced by 48 bytes.
>
> And its one of the documented way to handle this kind of problems
> (Documentation/atomic_ops.txt line 114)
>
> I guess we should amend this documentation, eventually.
>
> Thanks, please add you "Signed-off-by" if you agree with the patch.
>
Signed-off-by: Roman Gushchin <klamm@yandex-team.ru>
Many thanks to you, Paul E. McKenney and David Laight for your
patches, help and participation in this discussion.
>
> [PATCH] net: force a reload of first item in hlist_nulls_for_each_entry_rcu
>
> Roman Gushchin discovered that udp4_lib_lookup2() was not reloading
> first item in the rcu protected list, in case the loop was restarted.
>
> This produced soft lockups as in https://lkml.org/lkml/2013/4/16/37
>
> rcu_dereference(X)/ACCESS_ONCE(X) seem to not work as intended if X is
> ptr->field :
>
> In some cases, gcc caches the value or ptr->field in a register.
>
> Use a barrier() to disallow such caching, as documented in
> Documentation/atomic_ops.txt line 114
>
> Thanks a lot to Roman for providing analysis and numerous patches.
>
> Diagnosed-by: Roman Gushchin <klamm@yandex-team.ru>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Reported-by: Boris Zhmurov <zhmurov@yandex-team.ru>
> ---
> include/linux/rculist_nulls.h | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/rculist_nulls.h b/include/linux/rculist_nulls.h
> index 2ae1371..c7557fa 100644
> --- a/include/linux/rculist_nulls.h
> +++ b/include/linux/rculist_nulls.h
> @@ -105,9 +105,14 @@ static inline void hlist_nulls_add_head_rcu(struct hlist_nulls_node *n,
> * @head: the head for your list.
> * @member: the name of the hlist_nulls_node within the struct.
> *
> + * The barrier() is needed to make sure compiler doesn't cache first element [1],
> + * as this loop can be restarted [2]
> + * [1] Documentation/atomic_ops.txt around line 114
> + * [2] Documentation/RCU/rculist_nulls.txt around line 146
> */
> #define hlist_nulls_for_each_entry_rcu(tpos, pos, head, member) \
> - for (pos = rcu_dereference_raw(hlist_nulls_first_rcu(head)); \
> + for (({barrier();}), \
> + pos = rcu_dereference_raw(hlist_nulls_first_rcu(head)); \
> (!is_a_nulls(pos)) && \
> ({ tpos = hlist_nulls_entry(pos, typeof(*tpos), member); 1; }); \
> pos = rcu_dereference_raw(hlist_nulls_next_rcu(pos)))
>
>
next prev parent reply other threads:[~2013-05-30 8:25 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 9:05 [PATCH] " Roman Gushchin
2013-05-21 10:40 ` David Laight
2013-05-21 11:55 ` Roman Gushchin
2013-05-21 13:42 ` David Laight
2013-05-21 12:09 ` Paul E. McKenney
2013-05-21 12:46 ` Roman Gushchin
2013-05-21 12:58 ` Paul E. McKenney
2013-05-21 13:37 ` Eric Dumazet
2013-05-21 13:44 ` Eric Dumazet
2013-05-21 14:47 ` Roman Gushchin
2013-05-21 15:16 ` Eric Dumazet
2013-05-21 15:51 ` Roman Gushchin
2013-05-21 15:38 ` Eric Dumazet
2013-05-21 15:51 ` Roman Gushchin
2013-05-21 18:12 ` [PATCH v2] " Roman Gushchin
2013-05-22 2:01 ` Eric Dumazet
2013-05-22 5:49 ` Eric Dumazet
2013-05-22 11:58 ` Roman Gushchin
2013-05-22 12:30 ` Eric Dumazet
2013-05-22 13:07 ` Roman Gushchin
2013-05-22 17:45 ` Paul E. McKenney
2013-05-22 19:17 ` Roman Gushchin
2013-05-25 11:37 ` Paul E. McKenney
2013-05-27 11:34 ` Roman Gushchin
2013-05-27 17:55 ` Roman Gushchin
2013-05-28 0:12 ` Eric Dumazet
2013-05-28 9:10 ` Roman Gushchin
2013-05-29 0:34 ` Eric Dumazet
2013-05-29 1:31 ` Paul E. McKenney
2013-05-29 5:08 ` Eric Dumazet
2013-05-29 10:09 ` Roman Gushchin
2013-05-29 19:06 ` Eric Dumazet
2013-05-30 8:25 ` Roman Gushchin [this message]
2013-06-02 23:31 ` Eric Dumazet
2013-06-03 2:58 ` David Miller
2013-06-03 3:12 ` Eric Dumazet
2013-06-03 3:27 ` David Miller
2013-06-03 3:42 ` Paul E. McKenney
2013-06-03 3:47 ` Eric Dumazet
2013-06-03 3:49 ` David Miller
2013-06-03 6:05 ` Paul E. McKenney
2013-06-10 18:29 ` Boris B. Zhmurov
2013-06-10 18:51 ` Eric Dumazet
2013-06-03 3:48 ` Paul E. McKenney
2013-06-03 3:42 ` Paul E. McKenney
2013-05-29 9:17 ` Roman Gushchin
2013-05-29 1:19 ` Paul E. McKenney
2013-05-22 13:27 ` David Laight
2013-05-22 13:36 ` Eric Dumazet
2013-05-22 14:23 ` David Laight
2013-05-22 13:55 ` Roman Gushchin
2013-05-22 9:58 ` Paul E. McKenney
2013-05-22 12:28 ` Eric Dumazet
2013-05-22 13:00 ` Paul E. McKenney
2013-05-22 14:16 ` Eric Dumazet
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=51A70CF4.1020807@yandex-team.ru \
--to=klamm@yandex-team.ru \
--cc=David.Laight@ACULAB.COM \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=dipankar@in.ibm.com \
--cc=eric.dumazet@gmail.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=yoshfuji@linux-ipv6.org \
--cc=zhmurov@yandex-team.ru \
/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®