public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>, Ingo Molnar <mingo@elte.hu>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] rcu: fix lockdep for tracepoint
Date: Tue, 16 Mar 2010 06:31:15 -0700	[thread overview]
Message-ID: <20100316133115.GE6709@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100316130814.GA32375@Krystal>

On Tue, Mar 16, 2010 at 09:08:14AM -0400, Mathieu Desnoyers wrote:
> * Lai Jiangshan (laijs@cn.fujitsu.com) wrote:
> > tracepoint.h use rcu_dereference(), it triggers this warning:
> > 
> > [    0.701161] ===================================================
> > [    0.702211] [ INFO: suspicious rcu_dereference_check() usage. ]
> > [    0.702716] ---------------------------------------------------
> > [    0.703203] include/trace/events/workqueue.h:68 invoked rcu_dereference_check() without protection!
> > [    0.703971]
> > [    0.703990] other info that might help us debug this:
> > [    0.703993]
> > [    0.705590]
> > [    0.705604] rcu_scheduler_active = 1, debug_locks = 0
> > [    0.706712] 1 lock held by swapper/1:
> > [    0.707229]  #0:  (cpu_add_remove_lock){+.+.+.}, at: [<c0142f54>] cpu_maps_update_begin+0x14/0x20
> > [    0.710097]
> > [    0.710106] stack backtrace:
> > [    0.712602] Pid: 1, comm: swapper Not tainted 2.6.34-rc1-tip-01613-g72662bb #168
> > [    0.713231] Call Trace:
> > [    0.713997]  [<c017174d>] lockdep_rcu_dereference+0x9d/0xb0
> > [    0.714746]  [<c015a117>] create_workqueue_thread+0x107/0x110
> > [    0.715353]  [<c015aee0>] ? worker_thread+0x0/0x340
> > [    0.715845]  [<c015a8e8>] __create_workqueue_key+0x138/0x240
> > [    0.716427]  [<c0142f92>] ? cpu_maps_update_done+0x12/0x20
> > [    0.717012]  [<c086b12f>] init_workqueues+0x6f/0x80
> > [    0.717530]  [<c08576d2>] kernel_init+0x102/0x1f0
> > [    0.717570]  [<c08575d0>] ? kernel_init+0x0/0x1f0
> > [    0.718944]  [<c01030fa>] kernel_thread_helper+0x6/0x10
> > 
> > Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> 
> Acked-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> 
> Thanks Lai,

Me too!

Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>

> Mathieu
> 
> > ---
> > diff --git a/include/linux/tracepoint.h b/include/linux/tracepoint.h
> > index f59604e..78b4bd3 100644
> > --- a/include/linux/tracepoint.h
> > +++ b/include/linux/tracepoint.h
> > @@ -49,7 +49,7 @@ struct tracepoint {
> >  		void **it_func;						\
> >  									\
> >  		rcu_read_lock_sched_notrace();				\
> > -		it_func = rcu_dereference((tp)->funcs);			\
> > +		it_func = rcu_dereference_sched((tp)->funcs);		\
> >  		if (it_func) {						\
> >  			do {						\
> >  				((void(*)(proto))(*it_func))(args);	\
> > 
> 
> -- 
> Mathieu Desnoyers
> Operating System Efficiency Consultant
> EfficiOS Inc.
> http://www.efficios.com

  reply	other threads:[~2010-03-16 13:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16  9:00 [PATCH -tip] rcu: fix lockdep for tracepoint Lai Jiangshan
2010-03-16 13:08 ` Mathieu Desnoyers
2010-03-16 13:31   ` Paul E. McKenney [this message]
2010-03-16 14:47 ` [tip:core/urgent] rcu: Fix tracepoints & lockdep false positive tip-bot for Lai Jiangshan

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=20100316133115.GE6709@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@elte.hu \
    /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