Re: [PATCH 0/5] [GIT PULL] updates for tip/tracing/ftrace

["Paul E. McKenney" <paulmck@linux.vnet.ibm.com>]

On Fri, Mar 20, 2009 at 08:27:21PM +0100, Ingo Molnar wrote:
> 
> * Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> 
> > On Fri, Mar 20, 2009 at 07:38:49PM +0100, Ingo Molnar wrote:
> > > 
> > > * Ingo Molnar <mingo@elte.hu> wrote:
> > > 
> > > > > > This looks like it is RCU/stop_machine related. The CPU is 
> > > > > > stuck in in stop_machine? I see that rcu_torture is running. 
> > > > > > Does this go away if you turn off rcu_torture?
> > > > > 
> > > > > Grasping at straws...  Does Lai's rcu_barrier() fix help?
> > > > 
> > > > which one is that?
> > > 
> > > ok, found it. Will know in about ~24 hours whether it helps.
> > 
> > http://lkml.org/lkml/2009/3/20/71 was the one I was thinking of, 
> > just to double-check.
> 
> Yeah - i just picked it up into tip:core/rcu.
> 
> I didnt immediately connect the two things, as 'tracer self-test' 
> does not lend itself to 'CPU hotplug and RCU race fix' - but indeed 
> in the case of the function tracer there's a dependency due to 
> stop_machine_run(). Thanks for point it out!

Thanks go to Steve Rostedt -- I just followed up on his stack-trace
analysis here.  ;-)

						Thanx, Paul