From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Miller <davem@davemloft.net>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH RFC] hlist_add_tail_rcu disable sparse warning
Date: Wed, 23 Nov 2016 22:48:19 +0200 [thread overview]
Message-ID: <20161123223457-mutt-send-email-mst@kernel.org> (raw)
sparse is unhappy about this code in hlist_add_tail_rcu:
struct hlist_node *i, *last = NULL;
for (i = hlist_first_rcu(h); i; i = hlist_next_rcu(i))
last = i;
This is because hlist_next_rcu and hlist_next_rcu return
__rcu pointers.
The following trivial patch disables the warning
without changing the behaviour in any way.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
I would appreciate review to confirm the function doesn't
do anything unsafe though.
In particular, should this use __hlist_for_each_rcu instead?
I note that __hlist_for_each_rcu does rcu_dereference
internally, which is missing here.
compile-tested only.
diff --git a/include/linux/rculist.h b/include/linux/rculist.h
index 8beb98d..33574db 100644
--- a/include/linux/rculist.h
+++ b/include/linux/rculist.h
@@ -511,7 +511,7 @@ static inline void hlist_add_tail_rcu(struct hlist_node *n,
{
struct hlist_node *i, *last = NULL;
- for (i = hlist_first_rcu(h); i; i = hlist_next_rcu(i))
+ for (i = h->first; i; i = i->next)
last = i;
if (last) {
next reply other threads:[~2016-11-23 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 20:48 Michael S. Tsirkin [this message]
2016-11-26 0:52 ` [PATCH RFC] hlist_add_tail_rcu disable sparse warning David Miller
2016-11-28 14:39 ` Paul E. McKenney
2016-11-28 15:30 ` Michael S. Tsirkin
2016-12-05 3:47 ` Michael S. Tsirkin
2016-12-05 3:29 ` Michael S. Tsirkin
2016-12-05 19:37 ` Michael S. Tsirkin
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=20161123223457-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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