lkml.org 
[lkml]   [2017]   [Mar]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: lockdep warning: console vs. mem hotplug
On Sat, 25 Mar 2017 09:00:05 +0900
Sergey Senozhatsky <sergey.senozhatsky@gmail.com> 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/20170321044421.GB448@jagdpanzerIV.localdomain
>

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

\
 
 \ /
  Last update: 2017-03-25 02:01    [W:0.052 / U:20.384 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site