public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	linux-kernel@vger.kernel.org,
	Josh Triplett <josh@joshtriplett.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	David Miller <davem@davemloft.net>
Subject: Re: [PATCH] hlist_add_tail_rcu disable sparse warning
Date: Wed, 26 Apr 2017 07:02:57 -0700	[thread overview]
Message-ID: <20170426140257.GP3956@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170426091343.073af471@gandalf.local.home>

On Wed, Apr 26, 2017 at 09:13:43AM -0400, Steven Rostedt wrote:
> 
> Paul,
> 
> Did you see this email?

Yep! Michael's patch is 48ac34666ff7 ("hlist_add_tail_rcu disable sparse
warning") in -rcu and now in -tip.

But I do appreciate the reminder -- way too easy to miss stuff on LKML!

							Thanx, Paul

> -- Steve
> 
> 
> On Mon, 27 Feb 2017 20:26:01 +0200
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
> 
> > On Fri, Feb 10, 2017 at 07:39:49PM +0200, Michael S. Tsirkin wrote:
> > > 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.
> > > 
> > > It's a false positive - it's a write side primitive and so
> > > does not need to be called in a read side critical section.
> > > 
> > > The following trivial patch disables the warning
> > > without changing the behaviour in any way.
> > > 
> > > Note: __hlist_for_each_rcu would also remove the warning but it would be
> > > confusing since it calls rcu_derefence and is designed to run in the rcu
> > > read side critical section.
> > > 
> > > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > > ---  
> > 
> > ping
> > 
> > > changes since RFC
> > > 	added commit log text to explain why don't we use __hlist_for_each_rcu
> > > 
> > >  include/linux/rculist.h | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/include/linux/rculist.h b/include/linux/rculist.h
> > > index 4f7a956..bf578e8 100644
> > > --- a/include/linux/rculist.h
> > > +++ b/include/linux/rculist.h
> > > @@ -509,7 +509,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) {
> > > -- 
> > > MST  
> 

  reply	other threads:[~2017-04-26 14:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 17:39 [PATCH] hlist_add_tail_rcu disable sparse warning Michael S. Tsirkin
2017-02-27 18:26 ` Michael S. Tsirkin
2017-04-26 13:13   ` Steven Rostedt
2017-04-26 14:02     ` Paul E. McKenney [this message]
2017-02-27 18:40 ` Steven Rostedt

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=20170426140257.GP3956@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=davem@davemloft.net \
    --cc=jiangshanlai@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mst@redhat.com \
    --cc=rostedt@goodmis.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