From: Patrick McHardy <kaber@trash.net>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH] net: don't use INIT_RCU_HEAD
Date: Tue, 28 Oct 2008 16:29:06 +0100 [thread overview]
Message-ID: <49072FC2.8030801@trash.net> (raw)
In-Reply-To: <20081028133124.GA3006@x200.localdomain>
Alexey Dobriyan wrote:
> call_rcu() will unconditionally rewrite RCU head anyway.
> Applies to
> struct neigh_parms
> struct neigh_table
> struct net
> struct cipso_v4_doi
> struct in_ifaddr
> struct in_device
> rt->u.dst
It would probably make sense to get a statement from Paul
whether this might be required in the future, f.i. for some
debugging feature.
next prev parent reply other threads:[~2008-10-28 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 13:31 [PATCH] net: don't use INIT_RCU_HEAD Alexey Dobriyan
2008-10-28 15:29 ` Patrick McHardy [this message]
2008-10-28 15:43 ` Alexey Dobriyan
2008-10-28 16:05 ` Paul E. McKenney
2008-10-28 16:10 ` Paul E. McKenney
2008-10-28 20:25 ` David Miller
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=49072FC2.8030801@trash.net \
--to=kaber@trash.net \
--cc=adobriyan@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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).