Re: rcu: BUG: spinlock recursion on CPU#3, trinity-child19/5970

[Peter Zijlstra]

On Fri, 2012-06-29 at 23:40 +0200, Sasha Levin wrote:
> 
> The bad news are that what you saw was a lockdep enabled run
> (CONFIG_PROVE_RCU is enabled, and lockdep was enabled). There were no
> lockdep warnings at any point while reproducing it. 

rcu_switch_from() -> rcu_preempt_note_context_switch() is called _after_
the lockdep context switch annotation. Therefore lockdep things the prev
task isn't holding any locks anymore.


--
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/