From: Rongqing Li <rongqing.li@windriver.com>
To: "Yan, Zheng " <yanzheng@21cn.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH] Ipv6: Delete rcu_read_lock
Date: Thu, 29 Sep 2011 16:25:55 +0800 [thread overview]
Message-ID: <4E842B93.3010203@windriver.com> (raw)
In-Reply-To: <CAAM7YAnE4w4y6YWWxk0QGOX8Y6AZQHHQBuVMoRuSm=GtALAx=Q@mail.gmail.com>
On 09/29/2011 04:16 PM, Yan, Zheng wrote:
> I think the rcu_read_lock protects in6_dev->nd_parms.
>
It can not protect in6_dev->nd_parms.
rcu_read_lock protects the data which is accessed by rcu_XXX,
-Roy
> Yan, Zheng
--
Best Reagrds,
Roy | RongQing Li
next prev parent reply other threads:[~2011-09-29 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 7:46 [PATCH] Ipv6: Delete rcu_read_lock rongqing.li
2011-09-29 8:16 ` Yan, Zheng
2011-09-29 8:25 ` Rongqing Li [this message]
2011-09-29 8:52 ` Yan, Zheng
2011-09-29 9:10 ` Rongqing Li
2011-09-29 8:44 ` Eric Dumazet
2011-09-29 8:49 ` Rongqing Li
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=4E842B93.3010203@windriver.com \
--to=rongqing.li@windriver.com \
--cc=netdev@vger.kernel.org \
--cc=yanzheng@21cn.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.