public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, jkosina@suse.cz, bp@suse.de,
	yaneti@declera.com, jay.vosburgh@canonical.com, mroos@linux.ee,
	emunson@akamai.com, kevin@scrye.com
Subject: Re: [GIT PULL rcu/urgent-for-mingo] Regression fixes
Date: Thu, 30 Oct 2014 07:39:27 +0100	[thread overview]
Message-ID: <20141030063927.GC29004@gmail.com> (raw)
In-Reply-To: <20141029180721.GA9127@linux.vnet.ibm.com>


* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:

> Hello, Ingo,
> 
> This pull request contains a couple of fixes for RCU regressions:
> 
> 1.	Complete the work of commit dd56af42bd82 (rcu: Eliminate deadlock
> 	between CPU hotplug and expedited grace periods), which was
> 	intended to allow synchronize_sched_expedited() to be safely
> 	used when holding locks acquired by CPU-hotplug notifiers.
> 	This commit makes the put_online_cpus() avoid the deadlock
> 	instead of just handling the get_online_cpus().
> 
> 2.	Complete the work of commit 35ce7f29a44a (rcu: Create rcuo
> 	kthreads only for onlined CPUs), which was intended to allow
> 	RCU to avoid allocating unneeded kthreads on systems where the
> 	firmware says that there are more CPUs than are really present.
> 	This commit makes rcu_barrier() aware of the mismatch, so that
> 	it doesn't hang waiting for non-existent CPUs.  (And yes, I do
> 	need to force this non-existent-CPU condition into my testing.)
> 
> Both of these changes have been tested by the submitters and have been
> exposed to -next testing.  These changes are needed to avoid system hangs,
> and these system hangs have actually occurred during mainline testing.
> 
> These changes are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git urgent-for-mingo
> 
> for you to fetch changes up to d7e29933969e5ca7c112ce1368a07911f4485dc2:
> 
>   rcu: Make rcu_barrier() understand about missing rcuo kthreads (2014-10-28 13:24:13 -0700)
> 
> ----------------------------------------------------------------
> Paul E. McKenney (2):
>       rcu: More on deadlock between CPU hotplug and expedited grace periods
>       rcu: Make rcu_barrier() understand about missing rcuo kthreads
> 
>  include/trace/events/rcu.h | 18 +++++++++---------
>  kernel/cpu.c               | 14 +++++++++++++-
>  kernel/rcu/tree.c          | 15 ++++++++++-----
>  kernel/rcu/tree.h          |  1 +
>  kernel/rcu/tree_plugin.h   | 33 +++++++++++++++++++++++++++++++++
>  5 files changed, 66 insertions(+), 15 deletions(-)
> 

Pulled, thanks a lot Paul!

	Ingo

      reply	other threads:[~2014-10-30  6:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29 18:07 [GIT PULL rcu/urgent-for-mingo] Regression fixes Paul E. McKenney
2014-10-30  6:39 ` 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=20141030063927.GC29004@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@suse.de \
    --cc=emunson@akamai.com \
    --cc=jay.vosburgh@canonical.com \
    --cc=jkosina@suse.cz \
    --cc=kevin@scrye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=yaneti@declera.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