From: Ingo Molnar <mingo@elte.hu>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
a.p.zijlstra@chello.nl, tglx@linutronix.de
Subject: Re: [GIT PULL] RCU fixes for 2.6.34
Date: Tue, 4 May 2010 08:45:11 +0200 [thread overview]
Message-ID: <20100504064511.GC10464@elte.hu> (raw)
In-Reply-To: <20100504033616.GA6155@linux.vnet.ibm.com>
* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> Hello, Ingo,
>
> Here are RCU fixes for 2.6.34, mainly RCU-lockdep fixes:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git urgent-to-mingo
>
> This set excludes the three needing Acked-by, and also excludes the
> commits targeted for 2.6.35.
>
> Thanx, Paul
>
> ------------------>
> David Howells (2)
> KEYS: Fix an RCU warning in the reading of user keys
> KEYS: Fix an RCU warning
>
> Lai Jiangshan (1)
> rcu: v2: optionally leave lockdep enabled after RCU lockdep splat
>
> Li Zefan (4)
> cgroup: Check task_lock in task_subsys_state()
> sched: Fix an RCU warning in print_task()
> cgroup: Fix an RCU warning in alloc_css_id()
> cgroup: Fix an RCU warning in cgroup_path()
>
> include/linux/cgroup.h | 1 +
> include/linux/rcupdate.h | 15 +++++++++++----
> kernel/cgroup.c | 16 +++++++++++-----
> kernel/lockdep.c | 2 ++
> kernel/sched_debug.c | 2 ++
> lib/Kconfig.debug | 12 ++++++++++++
> security/keys/request_key.c | 13 ++++++++-----
> security/keys/user_defined.c | 3 ++-
> 8 files changed, 49 insertions(+), 15 deletions(-)
Pulled, thanks a lot Paul!!
Ingo
prev parent reply other threads:[~2010-05-04 6:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 3:36 [GIT PULL] RCU fixes for 2.6.34 Paul E. McKenney
2010-05-04 6:45 ` Ingo Molnar [this message]
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=20100504064511.GC10464@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--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 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.