On Sat, 25 Mar 2017 09:00:05 +0900 Sergey Senozhatsky <[email protected]> wrote:
> Hello, > > On (03/24/17 12:39), Steven Rostedt wrote: > [..] > > Is there a stack trace of where the lockdep dump happened? That is > > useful too. Otherwise we don't see where the inverse happened. > > Steven, isn't it the inversion I describe in [1] (after the first lockdep > warning)? > > [1] lkml.kernel.org/r/[email protected] > Yeah, I believe you are right. I just wanted to make sure. It's the same backtrace as the "(&(&sclp_con_lock)->rlock){-.-...}:" dump, but I wanted to make sure. -- Steve
