From: David Miller <davem@davemloft.net>
To: ying.xue@windriver.com
Cc: paulmck@linux.vnet.ibm.com, eric.dumazet@gmail.com,
jon.maloy@ericsson.com, erik.hugne@ericsson.com,
netdev@vger.kernel.org, kbuild-all@01.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next RESEND 0/2] fix rculist sparse errors
Date: Wed, 10 Dec 2014 13:49:21 -0500 (EST) [thread overview]
Message-ID: <20141210.134921.191006187867269911.davem@davemloft.net> (raw)
In-Reply-To: <1418201167-9591-1-git-send-email-ying.xue@windriver.com>
From: Ying Xue <ying.xue@windriver.com>
Date: Wed, 10 Dec 2014 16:46:05 +0800
> When hlist_for_each_entry_continue_rcu_bh() gets "next" pointer of
> hlist_node structure through rcu_dereference_bh(), sparse warning
> appears as the "next" pointer is not annotated as __rcu. So if
> the "next" pointer is accessed with hlist_next_rcu() macro, the
> __rcu annotation will be added to the pointer. As a consequence,
> sparse warning is eliminated too.
>
> The similar errors also appear in hlist_for_each_entry_continue_rcu()
> and hlist_for_each_entry_from_rcu().
>
> In this version, CC more people like Paul E. McKenney and lkml mail
> list.
The rculist.h changes should go via Paul's tree, not mine.
prev parent reply other threads:[~2014-12-10 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 8:46 [PATCH net-next RESEND 0/2] fix rculist sparse errors Ying Xue
2014-12-10 8:46 ` [PATCH net-next RESEND 1/2] tipc: fix RCU sparse error Ying Xue
2014-12-10 8:46 ` [PATCH net-next RESEND 2/2] ipv6: fix sparse warning Ying Xue
2014-12-10 16:04 ` Paul E. McKenney
2014-12-11 1:56 ` Ying Xue
2014-12-11 17:02 ` Paul E. McKenney
2014-12-10 18:49 ` 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=20141210.134921.191006187867269911.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=erik.hugne@ericsson.com \
--cc=jon.maloy@ericsson.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=ying.xue@windriver.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 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).