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>,
	Jens Axboe <jens.axboe@oracle.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	a.p.zijlstra@chello.nl, tglx@linutronix.de
Subject: Re: [GIT PULL] Additional RCU fixes for 2.6.34
Date: Thu, 6 May 2010 08:22:50 +0200	[thread overview]
Message-ID: <20100506062250.GC1172@elte.hu> (raw)
In-Reply-To: <20100506002838.GA31818@linux.vnet.ibm.com>


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

> Hello, Ingo,
> 
> Here are three more RCU-lockdep fixes for 2.6.34:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git rcu/urgent
> 
> 							Thanx, Paul
> 
> ------------------>
> Vivek Goyal <vgoyal@redhat.com> (1)
> 	blk-cgroup: Fix RCU correctness warning in cfq_init_queue()
> 
> Paul E. McKenney <paulmck@linux.vnet.ibm.com> (2)
> 	vfs: fix RCU-lockdep false positive due to /proc access
> 	memcg: css_id() must be called under rcu_read_lock()
> 
>  block/cfq-iosched.c      |    2 ++
>  include/linux/fdtable.h  |    3 ++-
>  include/linux/rcupdate.h |   11 +++++++++++
>  kernel/rcupdate.c        |   11 +++++++++++
>  mm/memcontrol.c          |   21 ++++++++++++++++-----
>  5 files changed, 42 insertions(+), 6 deletions(-)

Pulled, thanks Paul!

Jens, is that blk-cgroup fix from Vivek fine to you via this route?

Thanks,

	Ingo

  reply	other threads:[~2010-05-06  6:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06  0:28 [GIT PULL] Additional RCU fixes for 2.6.34 Paul E. McKenney
2010-05-06  6:22 ` Ingo Molnar [this message]
2010-05-06  6:25   ` Jens Axboe
2010-05-06  6:39     ` Ingo Molnar
2010-05-06  6:43       ` Jens Axboe
2010-05-06  6:49         ` Ingo Molnar
2010-05-06  6:54           ` Jens Axboe

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=20100506062250.GC1172@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox