[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120612152521.GD2423@linux.vnet.ibm.com>
Date: Tue, 12 Jun 2012 08:25:21 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Peter Zijlstra <peterz@...radead.org>,
Sasha Levin <levinsasha928@...il.com>,
Ingo Molnar <mingo@...e.hu>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Dave Jones <davej@...hat.com>
Subject: Re: rcu,sched: spinlock recursion on 3.5-rc2
On Tue, Jun 12, 2012 at 05:20:10PM +0200, Thomas Gleixner wrote:
> On Tue, 12 Jun 2012, Peter Zijlstra wrote:
>
> > On Tue, 2012-06-12 at 17:07 +0200, Thomas Gleixner wrote:
> > > Hmm, not sure. The deadlock was not triggered in switch_to. It was
> > > just at the beginning of __schedule()
> > >
> > >
> > How can you tell? switch_to() is a macro not a function, it won't ever
> > show up on a stack-trace.. but I think you meant context_switch() but
> > that typically gets inlined, similar problem.
>
> Bah, I misread the trace and the rcu code. :(
>
> So, yes the revert should solve the problem. Looks like I need more
> coffee, not Paul :)
Well, given that the commit that I reverted was my own, I definitely
needed more of something or another... :-)
Thanx, Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists