From: Peter Zijlstra <peterz@infradead.org>
To: Mike Galbraith <efault@gmx.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Byungchul Park <max.byungchul.park@gmail.com>
Subject: Re: hotplug lockdep splat (tip)
Date: Mon, 4 Sep 2017 09:55:02 +0200 [thread overview]
Message-ID: <20170904075502.74pgfd2twdfklspw@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1504421975.30792.32.camel@gmx.de>
On Sun, Sep 03, 2017 at 08:59:35AM +0200, Mike Galbraith wrote:
>
> [ 126.626908] Unregister pv shared memory for cpu 1
> [ 126.631041]
> [ 126.631269] ======================================================
> [ 126.632442] WARNING: possible circular locking dependency detected
> [ 126.633599] 4.13.0.g06260ca-tip-lockdep #2 Tainted: G E
> [ 126.634380] ------------------------------------------------------
> [ 126.635124] stress-cpu-hotp/3156 is trying to acquire lock:
> [ 126.635804] ((complete)&st->done){+.+.}, at: [<ffffffff8108d19a>] takedown_cpu+0x8a/0xf0
> [ 126.636809]
> [ 126.636809] but task is already holding lock:
> [ 126.637567] (sparse_irq_lock){+.+.}, at: [<ffffffff81107ac7>] irq_lock_sparse+0x17/0x20
> [ 126.638665]
https://lkml.kernel.org/r/20170829193416.GC32112@worktop.programming.kicks-ass.net
I still need to write a coherent Changelog and comments for that :/
next prev parent reply other threads:[~2017-09-04 7:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-02 11:09 hotplug lockdep splat (tip-rt) Mike Galbraith
2017-09-03 6:59 ` hotplug lockdep splat (tip) Mike Galbraith
2017-09-04 7:55 ` Peter Zijlstra [this message]
2017-09-04 13:27 ` Mike Galbraith
2017-09-04 14:24 ` Peter Zijlstra
2017-09-04 16:31 ` Mike Galbraith
2017-09-04 16:54 ` Mike Galbraith
2017-09-04 15:37 ` Peter Zijlstra
2017-09-04 17:02 ` Mike Galbraith
2017-09-04 19:44 ` Peter Zijlstra
2017-09-04 14:23 ` Peter Zijlstra
2017-09-04 17:15 ` Mike Galbraith
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=20170904075502.74pgfd2twdfklspw@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=max.byungchul.park@gmail.com \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®