linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <dahi@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@kernel.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org,
	Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [GIT PULL rcu/next] RCU commits for 3.20
Date: Tue, 3 Feb 2015 15:34:45 +0100	[thread overview]
Message-ID: <20150203153445.296bc07f@thinkpad-w530> (raw)
In-Reply-To: <20150121051514.GA12032@gmail.com>

> 
> * Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> 
> > Hello, Ingo,
> > 
> > The changes in this series include:
> > 
> > 1.	Documentation updates.  These were posted to LKML at
> > 	https://lkml.org/lkml/2015/1/7/496.
> > 
> > 2.	Miscellaneous fixes.  These were posted to LKML at
> > 	https://lkml.org/lkml/2015/1/7/507.
> > 
> > 3.	Preemptible-RCU fixes, including fixing an old bug in the
> > 	interaction of RCU priority boosting and CPU hotplug.  These were
> > 	posted to LKML at https://lkml.org/lkml/2015/1/7/535.
> > 
> > 4.	SRCU updates.  These were posted to LKML at
> > 	https://lkml.org/lkml/2015/1/7/555.
> > 
> > 5.	RCU CPU stall-warning updates.  These were posted to LKML at
> > 	https://lkml.org/lkml/2015/1/7/565.
> > 
> > 6.	RCU torture-test updates.  These were posted to LKML at
> > 	https://lkml.org/lkml/2015/1/7/591.
> > 
> > These changes are available in the git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git for-mingo
> > 
> > for you to fetch changes up to 78e691f4ae2d5edea0199ca802bb505b9cdced88:
> > 
> >   Merge branches 'doc.2015.01.07a', 'fixes.2015.01.15a', 'preempt.2015.01.06a', 'srcu.2015.01.06a', 'stall.2015.01.16a' and 'torture.2015.01.11a' into HEAD (2015-01-15 23:34:34 -0800)
> > 
> > ----------------------------------------------------------------
> > 
> > Alexander Gordeev (1):
> >       rcu: Remove redundant rcu_is_cpu_rrupt_from_idle() from tiny RCU
> > 
> > Calvin Owens (1):
> >       ksoftirqd: Enable IRQs and call cond_resched() before poking RCU
> > 
> > David Hildenbrand (1):
> >       hotplugcpu: Avoid deadlocks by waking active_writer
> > 

Hi Ingo, Paul,

Heiko/Christian seem to have hit the bug (hotplugcpu: Avoid deadlocks by waking
active_writer addresses) in 3.18-rc3.

And as commit b2c4623dcd07 was in linux starting with 3.18-rc3, we should
probably (have done a) cc-stable.

David


  reply	other threads:[~2015-02-03 14:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20  0:45 [GIT PULL rcu/next] RCU commits for 3.20 Paul E. McKenney
2015-01-21  5:15 ` Ingo Molnar
2015-02-03 14:34   ` David Hildenbrand [this message]
2015-02-03 16:34     ` Paul E. McKenney
2015-02-06 18:28       ` Ingo Molnar
2015-02-06 18:56         ` Paul E. McKenney
2015-02-09  7:56           ` Ingo Molnar
2015-02-09 13:50             ` Paul E. McKenney
2015-02-09 17:45               ` Ingo Molnar
2015-02-09 19:43                 ` Paul E. McKenney
2015-02-10  8:19                 ` David Hildenbrand
2015-02-10 18:34                   ` 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=20150203153445.296bc07f@thinkpad-w530 \
    --to=dahi@linux.vnet.ibm.com \
    --cc=ehrhardt@linux.vnet.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulmck@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).