From: Jens Axboe <jens.axboe@oracle.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
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:43:36 +0200 [thread overview]
Message-ID: <20100506064336.GP27497@kernel.dk> (raw)
In-Reply-To: <20100506063948.GG1172@elte.hu>
On Thu, May 06 2010, Ingo Molnar wrote:
>
> * Jens Axboe <jens.axboe@oracle.com> wrote:
>
> > On Thu, May 06 2010, Ingo Molnar wrote:
> > >
> > > * 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?
> >
> > Sure, I did think it was a bit odd to funnel it through that route, but it's
> > no big deal.
>
> I havent pushed the tree out yet, wanted to wait for your feedback before
> doing anything permanent. You can still apply it to the block tree.
>
> You were Cc:-ed 3 days ago to this patch, when RCU fixes got posted. These are
> basically the leftover PROVE_RCU fix patches that didnt get picked up by
> subsystem trees.
Yes I read it then, and Paul said he'd applied it. So I didn't touch it,
it was trivial enough that the path to the kernel wasn't that big of a
problem. And it didn't cause me any merge issues, so no harm done.
I can easily pull it in since I have a fix or two for .34 left yet, but
if you already have it stashed and ready to submit, lets just leave it
there.
--
Jens Axboe
next prev parent reply other threads:[~2010-05-06 6:43 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
2010-05-06 6:25 ` Jens Axboe
2010-05-06 6:39 ` Ingo Molnar
2010-05-06 6:43 ` Jens Axboe [this message]
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=20100506064336.GP27497@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox