From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu, 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: [PATCH tip/core/rcu 0/3] rcu: fix !PREEMPT, __mpol_dup(), and ftrace_perf_buf_prepare() RCU lockdep splats
Date: Wed, 3 Mar 2010 17:50:01 -0800 [thread overview]
Message-ID: <20100304015001.GA32190@linux.vnet.ibm.com> (raw)
Hello!
This patch fixes three RCU lockdep issues:
1. Makes rcu_read_lock_sched_held() correctly handle !PREEMPT
kernels.
2. Suppresses __mpol_dup() false positive.
3. Converts a pair of rcu_dereference() calls in
ftrace_perf_buf_prepare() to rcu_dereference_sched().
There are probably more where these came from. ;-)
Thanx, Paul
------------------------------------------------------------------------
include/linux/rcupdate.h | 15 ++++++++++++++-
include/trace/ftrace.h | 4 ++--
kernel/trace/trace_event_profile.c | 5 ++---
mm/mempolicy.c | 3 ++-
4 files changed, 20 insertions(+), 7 deletions(-)
next reply other threads:[~2010-03-04 1:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 1:50 Paul E. McKenney [this message]
2010-03-04 1:50 ` [PATCH tip/core/rcu 1/3] rcu: Make rcu_read_lock_sched_held() handle !PREEMPT Paul E. McKenney
2010-03-04 16:32 ` [tip:core/urgent] " tip-bot for Paul E. McKenney
2010-03-04 1:50 ` [PATCH tip/core/rcu 2/3] rcu: suppress __mpol_dup() false positive from RCU lockdep Paul E. McKenney
2010-03-04 16:32 ` [tip:core/urgent] rcu: Suppress " tip-bot for Paul E. McKenney
2010-03-04 1:50 ` [PATCH tip/core/rcu 3/3] rcu, ftrace: fix RCU lockdep splat in ftrace_perf_buf_prepare() Paul E. McKenney
2010-03-04 3:55 ` Frederic Weisbecker
2010-03-04 16:33 ` [tip:core/urgent] rcu, ftrace: Fix " tip-bot for 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=20100304015001.GA32190@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--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=mingo@elte.hu \
--cc=niv@us.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 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.