From: David Miller <davem@davemloft.net>
To: bernat.ada@gmail.com
Cc: kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
kaber@trash.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, paulmck@linux.vnet.ibm.com
Subject: Re: [PATCH] ipv6: sit: Replace rcu_assign_pointer() with RCU_INIT_POINTER()
Date: Wed, 27 Aug 2014 18:07:03 -0700 (PDT) [thread overview]
Message-ID: <20140827.180703.431737353995283706.davem@davemloft.net> (raw)
In-Reply-To: <20140826134632.GA1473@ada>
From: Andreea-Cristina Bernat <bernat.ada@gmail.com>
Date: Tue, 26 Aug 2014 16:46:32 +0300
> According to RCU_INIT_POINTER()'s block comment 3.a, it can be used if
> "3. The referenced data structure has already been exposed to readers either
> at compile time or via rcu_assign_pointer() -and-
> a. You have not made -any- reader-visible changes to this structure since
> then".
>
> This case fulfills the conditions above because between the rtnl_dereference()
> call and the rcu_assign_pointer() call there is no update of that value.
> Therefore, this patch makes the replacement.
>
> The following Coccinelle semantic patch was used:
> @@
> @@
>
> - rcu_assign_pointer
> + RCU_INIT_POINTER
> (...,
> (
> rtnl_dereference(...)
> |
> rcu_dereference_protected(...)
> ) )
>
> Signed-off-by: Andreea-Cristina Bernat <bernat.ada@gmail.com>
These changes are not correct.
We need the memory barrier added by rcu_assign_pointer(), which occurs
before the assignment, otherwise the RCU pointer update might be visible
before the stores that initialize the rest of the structure in question.
I'm not applying any of these patches, sorry.
prev parent reply other threads:[~2014-08-28 1:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 13:46 [PATCH] ipv6: sit: Replace rcu_assign_pointer() with RCU_INIT_POINTER() Andreea-Cristina Bernat
2014-08-28 1:07 ` David Miller [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=20140827.180703.431737353995283706.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bernat.ada@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 \
/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;
as well as URLs for NNTP newsgroup(s).