From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Milos Vyletel <milos@redhat.com>,
Josh Triplett <josh@joshtriplett.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Jonathan Corbet <corbet@lwn.net>,
"open list:READ-COPY UPDATE..." <linux-kernel@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
jeff.haran@citrix.com
Subject: Re: [PATCH] rcu: small rcu_dereference doc update
Date: Fri, 17 Apr 2015 07:24:36 -0700 [thread overview]
Message-ID: <20150417142436.GN23685@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150417101350.07193a09@gandalf.local.home>
On Fri, Apr 17, 2015 at 10:13:50AM -0400, Steven Rostedt wrote:
> On Fri, 17 Apr 2015 07:06:38 -0700
> "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
>
> > On Fri, Apr 17, 2015 at 12:33:36PM +0200, Milos Vyletel wrote:
> > > Make a note stating that repeated calls of rcu_dereference() may not
> > > return the same pointer if update happens while in critical section.
> > >
> > > Reported-by: Jeff Haran <jeff.haran@citrix.com>
> > > Signed-off-by: Milos Vyletel <milos@redhat.com>
> >
> > Hmmm... Seems like that should be obvious, but on the other hand,
> > I have been using RCU for more than twenty years, so my obviousness
> > sensors might need recalibration.
> >
> > Queued for 4.2.
>
> Before you queue it, there's a few articles that are screaming to be
> present...
OK, I removed it. Milos, when you send me a version that Steve is happy
with, I will requeue it.
Thanx, Paul
> > > ---
> > > Documentation/RCU/whatisRCU.txt | 4 +++-
> > > 1 file changed, 3 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/Documentation/RCU/whatisRCU.txt b/Documentation/RCU/whatisRCU.txt
> > > index 88dfce1..82b1b2c 100644
> > > --- a/Documentation/RCU/whatisRCU.txt
> > > +++ b/Documentation/RCU/whatisRCU.txt
> > > @@ -256,7 +256,9 @@ rcu_dereference()
> > > If you are going to be fetching multiple fields from the
> > > RCU-protected structure, using the local variable is of
> > > course preferred. Repeated rcu_dereference() calls look
> > > - ugly and incur unnecessary overhead on Alpha CPUs.
> > > + ugly, do not guarantee that same pointer will be returned
> > > + if update happened while in critical section and incur
> > > + unnecessary overhead on Alpha CPUs.
>
> ugly, do not guarantee that the same pointer will be returned
> if an update happened while in the critical section, and incur
> unnecessary overhead on Alpha CPUs.
>
> -- Steve
>
> > >
> > > Note that the value returned by rcu_dereference() is valid
> > > only within the enclosing RCU read-side critical section.
> > > --
> > > 2.1.0
> > >
>
next prev parent reply other threads:[~2015-04-17 14:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 10:33 [PATCH] rcu: small rcu_dereference doc update Milos Vyletel
2015-04-17 14:06 ` Paul E. McKenney
2015-04-17 14:13 ` Steven Rostedt
2015-04-17 14:24 ` Paul E. McKenney [this message]
2015-04-17 14:37 ` Milos Vyletel
2015-04-17 16:53 ` Jeff Haran
2015-04-17 18:40 ` Paul E. McKenney
2015-04-17 23:48 ` Jeff Haran
2015-04-21 15:53 ` Paul E. McKenney
2015-04-17 15:55 ` Pranith Kumar
2015-04-17 16:15 ` Paul E. McKenney
2015-04-17 17:13 ` Pranith Kumar
2015-04-17 21:27 ` 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=20150417142436.GN23685@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=corbet@lwn.net \
--cc=jeff.haran@citrix.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=milos@redhat.com \
--cc=rostedt@goodmis.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