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/20170321044421.GB448@jagdpanzerIV.localdomain
-ss
