Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1609051
| From | Steven Rostedt <rostedt@goodmis.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: lockdep warning: console vs. mem hotplug |
| Date | 2017-03-25 02:10 +0100 |
| Message-ID | <toInn-1Fh-7@gated-at.bofh.it> (permalink) |
| References | <tn9i1-7Yx-9@gated-at.bofh.it> <toApP-4fB-5@gated-at.bofh.it> <toHrk-ZP-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: lockdep warning: console vs. mem hotplug Steven Rostedt <rostedt@goodmis.org> - 2017-03-24 17:40 +0100
Re: lockdep warning: console vs. mem hotplug Sebastian Ott <sebott@linux.vnet.ibm.com> - 2017-03-24 18:00 +0100
Re: lockdep warning: console vs. mem hotplug Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2017-03-25 01:10 +0100
Re: lockdep warning: console vs. mem hotplug Steven Rostedt <rostedt@goodmis.org> - 2017-03-25 02:10 +0100
csiph-web