From: Suzanne Wood <suzannew@cs.pdx.edu>
To: herbert@gondor.apana.org.au
Cc: Robert.Olsson@data.slu.se, davem@davemloft.net,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
paulmck@us.ibm.com, walpole@cs.pdx.edu
Subject: Re: [RFC][PATCH] identify in_dev_get rcu read-side critical sections
Date: Thu, 29 Sep 2005 16:39:57 -0700 (PDT) [thread overview]
Message-ID: <200509292339.j8TNdvKc019657@rastaban.cs.pdx.edu> (raw)
> From suzannew Thu Sep 29 16:30:28 2005
> > From: Herbert Xu 30 Sep 2005 07:28
> > BTW, could you please move the rcu_dereference in in_dev_get()
> > into the if clause? The barrier is not needed when ip_ptr is
> > NULL.
> The trouble with that may be that there are three events, the
> dereference, the assignment, and the conditional test. The
> rcu_dereference() is meant to assure deferred destruction
> throughout.
Sorry, I was thinking in terms of the rcu_read_lock, so this is misstated.
next reply other threads:[~2005-09-29 23:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 23:39 Suzanne Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-01 18:37 [RFC][PATCH] identify in_dev_get rcu read-side critical sections Suzanne Wood
2005-10-01 19:29 ` Herbert Xu
2005-10-01 18:00 Suzanne Wood
2005-10-01 6:56 Suzanne Wood
2005-10-01 7:12 ` Herbert Xu
2005-10-01 18:04 ` Paul E. McKenney
2005-09-30 1:06 Suzanne Wood
2005-10-01 1:13 ` Herbert Xu
2005-09-29 23:59 Suzanne Wood
2005-09-30 0:23 ` Herbert Xu
2005-09-29 23:30 Suzanne Wood
2005-09-30 0:21 ` Herbert Xu
2005-09-30 0:23 ` Paul E. McKenney
2005-09-30 0:27 ` Herbert Xu
2005-09-30 0:36 ` Paul E. McKenney
2005-09-30 1:04 ` Herbert Xu
2005-09-30 1:16 ` Paul E. McKenney
2005-09-30 1:19 ` Herbert Xu
2005-09-29 16:02 Suzanne Wood
2005-09-29 21:28 ` Herbert Xu
2005-09-28 0:22 Suzanne Wood
2005-09-08 17:12 Suzanne Wood
2005-09-27 20:56 ` David S. Miller
2005-09-28 2:55 ` Herbert Xu
2005-09-28 14:51 ` Paul E. McKenney
2005-09-28 22:11 ` Herbert Xu
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=200509292339.j8TNdvKc019657@rastaban.cs.pdx.edu \
--to=suzannew@cs.pdx.edu \
--cc=Robert.Olsson@data.slu.se \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=paulmck@us.ibm.com \
--cc=walpole@cs.pdx.edu \
/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).