public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, laijs@cn.fujitsu.com,
	dipankar@in.ibm.com, akpm@linux-foundation.org,
	mathieu.desnoyers@polymtl.ca, josh@joshtriplett.org,
	dvhltc@us.ibm.com, niv@us.ibm.com, tglx@linutronix.de,
	peterz@infradead.org, rostedt@goodmis.org,
	Valdis.Kletnieks@vt.edu, dhowells@redhat.com
Subject: Re: [PATCH tip/core/rcu 0/2] rcu: fixes for RCU lockdep
Date: Sat, 27 Feb 2010 10:51:15 +0100	[thread overview]
Message-ID: <20100227095115.GF31794@elte.hu> (raw)
In-Reply-To: <20100226174248.GF6733@linux.vnet.ibm.com>


* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:

> On Fri, Feb 26, 2010 at 12:50:18PM +0100, Ingo Molnar wrote:
> > 
> > * Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> > 
> > > Hello!
> > > 
> > > This set fixes a couple of problems with the RCU-based lockdep patches:
> > > 
> > > 1.	Make the lockdep_rcu_dereference() message less alarmist
> > > 
> > > 2.	Make rcu_read_lock_sched_held() take boot-time lack of
> > > 	preemption into account.
> > > 
> > > 							Thanx, Paul
> > > 
> > > ------------------------------------------------------------------------
> > > 
> > >  include/linux/rcupdate.h |    4 +++-
> > >  include/linux/rcutiny.h  |    4 ----
> > >  include/linux/rcutree.h  |    1 -
> > >  kernel/lockdep.c         |    7 +++----
> > >  kernel/rcupdate.c        |   18 ++++++++++++++++++
> > >  kernel/rcutree.c         |   20 --------------------
> > >  6 files changed, 24 insertions(+), 30 deletions(-)
> > 
> > Applied, thanks Paul!
> > 
> > Here's a new warning:
> > 
> > [    0.000000] 
> > [    0.000000] ===================================================
> > [    0.000000] [ INFO: suspicious rcu_dereference_check() usage. ]
> > [    0.000000] ---------------------------------------------------
> > [    0.000000] kernel/sched_fair.c:3469 invoked rcu_dereference_check() without protection!
> 
> Hmmm...  Could you please tell me what commit this test ran against?

One version of tip:master :-/

ob'kconfig - i think this header bit of the .config:

> > # Automatically generated make config: don't edit
> > # Linux kernel version: 2.6.33
> > # Fri Feb 26 14:51:28 2010

should contain the last-seen kernel Git sha1 as well. It would ease things 
considerably.

> My guesses thus far either don't have that many lines in kernel/sched_fair.c 
> or have some unrelated code at line 3469.

I'll post the sha1 next time i encounter this warning.

Thanks,

	Ingo

  reply	other threads:[~2010-02-27  9:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25 22:06 [PATCH tip/core/rcu 0/2] rcu: fixes for RCU lockdep Paul E. McKenney
2010-02-25 22:06 ` [PATCH tip/core/rcu 1/2] rcu: make lockdep_rcu_dereference() message less alarmist Paul E. McKenney
2010-02-26  9:29   ` [tip:core/rcu] rcu: Make " tip-bot for Paul E. McKenney
2010-02-25 22:06 ` [PATCH tip/core/rcu 2/2] rcu: make rcu_read_lock_sched_held() take boot time into account Paul E. McKenney
2010-02-26  9:29   ` [tip:core/rcu] rcu: Make " tip-bot for Paul E. McKenney
2010-02-26  3:02 ` [PATCH tip/core/rcu] rcu: export rcu_scheduler_active Paul E. McKenney
2010-02-26  9:29   ` [tip:core/rcu] rcu: Export rcu_scheduler_active tip-bot for Paul E. McKenney
2010-02-26 11:50 ` [PATCH tip/core/rcu 0/2] rcu: fixes for RCU lockdep Ingo Molnar
2010-02-26 13:19   ` Ingo Molnar
2010-02-26 14:46     ` Ingo Molnar
2010-02-26 17:02     ` Paul E. McKenney
2010-02-26 17:42   ` Paul E. McKenney
2010-02-27  9:51     ` Ingo Molnar [this message]
2010-02-27 12:59       ` Ingo Molnar
2010-02-27 22:48         ` Paul E. McKenney

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=20100227095115.GF31794@elte.hu \
    --to=mingo@elte.hu \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=dvhltc@us.ibm.com \
    --cc=josh@joshtriplett.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=niv@us.ibm.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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