All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	tglx@linutronix.de, daniel.blueman@gmail.com,
	lizf@cn.fujitsu.com, miles.lane@gmail.com,
	manfred@colorfullife.com
Subject: Re: [GIT PULL rcu/urgent] yet more lockdep-RCU splat fixes
Date: Wed, 16 Jun 2010 08:23:51 +0200	[thread overview]
Message-ID: <1276669431.1745.595.camel@laptop> (raw)
In-Reply-To: <20100616055358.GB17936@elte.hu>

On Wed, 2010-06-16 at 07:53 +0200, Ingo Molnar wrote:
> * Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> 
> > Hello, Ingo,
> > 
> > Here are a few more fixes for RCU-lockdep splats.
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git rcu/urgent
> > 
> > This is based off of v2.6.35-rc3.
> > 
> > 							Thanx, Paul
> > 
> > ------------------>
> > Daniel J Blueman (1):
> >       rcu: fix lockdep splat in wake_affine()
> > 
> > Paul E. McKenney (2):
> >       rcu: fix scope of wake_affine()'s new RCU read-side critical section
> >       idr: fix RCU lockdep splat in idr_get_next()
> > 
> >  kernel/sched_fair.c |    2 ++
> >  lib/idr.c           |    4 ++--
> >  2 files changed, 4 insertions(+), 2 deletions(-)
> 
> Pulled, thanks a lot Paul!

I'm not at all sure of those two wake_affine() ones..

  reply	other threads:[~2010-06-16  6:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16  4:22 [GIT PULL rcu/urgent] yet more lockdep-RCU splat fixes Paul E. McKenney
2010-06-16  5:53 ` Ingo Molnar
2010-06-16  6:23   ` Peter Zijlstra [this message]
2010-06-16 22:41     ` Paul E. McKenney
2010-06-17  8:49       ` Peter Zijlstra
2010-06-22 20:44         ` Paul E. McKenney
2010-06-23  8:08           ` Peter Zijlstra

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=1276669431.1745.595.camel@laptop \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=daniel.blueman@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=manfred@colorfullife.com \
    --cc=miles.lane@gmail.com \
    --cc=mingo@elte.hu \
    --cc=paulmck@linux.vnet.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.