From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mingo@elte.hu
Cc: sergey.senozhatsky@gmail.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL rcu/urgent] rcu: Permit call_rcu() from CPU_DYING notifiers
Date: Mon, 16 Apr 2012 14:39:16 -0700 [thread overview]
Message-ID: <20120416213916.GA6458@linux.vnet.ibm.com> (raw)
Hello, Ingo,
The single commit in this pull request fixes a regression spotted
by Sergey Senozhatsky (https://lkml.org/lkml/2012/4/2/34). The
underlying problem is that some CPU_DYING notifiers post RCU
callbacks from a CPU that has been marked offline. The long-term
fix is to adopt those callbacks from RCU's CPU_DEAD notifier in
the 3.5 release. For 3.4, this commit simply shuts off the warning.
(Yes, the warning will return in 3.5 also.)
This change is available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/urgent
Thanx, Paul
-------------------->
Paul E. McKenney (1):
rcu: Permit call_rcu() from CPU_DYING notifiers
kernel/rcutree.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
reply other threads:[~2012-04-16 21:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120416213916.GA6458@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sergey.senozhatsky@gmail.com \
/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