Re: [GIT PULL rcu/next] RCU commits for 3.20
From: David Hildenbrand
Date: Tue Feb 03 2015 - 09:35:00 EST
>
> * Paul E. McKenney <paulmck@xxxxxxxxxxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/