From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sebastian Ott <sebott@linux.vnet.ibm.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Petr Mladek <pmladek@suse.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: lockdep warning: console vs. mem hotplug
Date: Sat, 25 Mar 2017 09:00:05 +0900 [thread overview]
Message-ID: <20170325000005.GC6356@tigerII.localdomain> (raw)
In-Reply-To: <20170324123933.78f9c125@gandalf.local.home>
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
next prev parent reply other threads:[~2017-03-25 0:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 16:43 lockdep warning: console vs. mem hotplug Sebastian Ott
2017-03-21 4:44 ` Sergey Senozhatsky
2017-03-21 5:04 ` Sergey Senozhatsky
2017-03-25 0:04 ` Sergey Senozhatsky
2017-03-25 1:08 ` Steven Rostedt
2017-03-25 1:37 ` Sergey Senozhatsky
2017-03-25 10:59 ` Sebastian Ott
2017-03-28 14:22 ` Michal Hocko
2017-03-28 16:00 ` Petr Mladek
2017-03-29 7:31 ` Michal Hocko
2017-03-30 9:45 ` Petr Mladek
2017-03-30 3:59 ` Sergey Senozhatsky
2017-07-24 12:46 ` Sebastian Ott
2017-07-24 13:32 ` Sergey Senozhatsky
2017-03-24 16:39 ` Steven Rostedt
2017-03-24 16:57 ` Sebastian Ott
2017-03-25 0:00 ` Sergey Senozhatsky [this message]
2017-03-25 1:00 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170325000005.GC6356@tigerII.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sebott@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.