From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, fweisbec@gmail.com, kirill@shutemov.name
Subject: [GIT PULL rcu/urgent] Fixes for RCU regressions
Date: Thu, 11 Oct 2012 10:22:37 -0700 [thread overview]
Message-ID: <20121011172237.GA32051@linux.vnet.ibm.com> (raw)
Hello, Ingo,
This series fixes some RCU regressions in 3.7.
Kirill A. Shutemov found a case where synchronize_rcu() is invoked
from a CPU-hotplug notifier, which, with RCU's shiny new kthread-based
grace-period implementation, results in deadlock. The first commit
in this series fixes this deadlock by introducing RCU-specific
synchronization, so that RCU grace periods exclude only RCU's CPU-hotplug
notifiers, not the entire CPU-hotplug operation. Kirill successfully
tested this commit (as have I), and it has furthermore been exposed to
-next testing.
The other commit in this series adds a warning to the new RCU_USER_QS
and RCU_USER_QS_FORCE Kconfig options, noting that these features,
though reasonably stable, are probably not ready for millions of users.
This commit affects only the Kconfig help text.
These changes are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/urgent
Thanx, Paul
------------------>
Frederic Weisbecker (1):
rcu: Advise most users not to enable RCU user mode
Paul E. McKenney (1):
rcu: Grace-period initialization excludes only RCU notifier
init/Kconfig | 12 ++++++++++++
kernel/rcutree.c | 21 ++++++++++-----------
kernel/rcutree.h | 6 ++++++
3 files changed, 28 insertions(+), 11 deletions(-)
next reply other threads:[~2012-10-11 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 17:22 Paul E. McKenney [this message]
2012-10-12 7:53 ` [GIT PULL rcu/urgent] Fixes for RCU regressions Ingo Molnar
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=20121011172237.GA32051@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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