From: Peter Zijlstra <peterz@infradead.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Boqun Feng <boqun.feng@gmail.com>, Ingo Molnar <mingo@redhat.com>,
Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] lockdep: report name and key when look_up_lock_class() got confused
Date: Mon, 19 Sep 2022 12:48:23 +0200 [thread overview]
Message-ID: <YyhI93taOenZMHrY@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <bd99391e-f787-efe9-5ec6-3c6dc4c587b0@I-love.SAKURA.ne.jp>
On Mon, Sep 19, 2022 at 09:52:13AM +0900, Tetsuo Handa wrote:
> Printing this information will be helpful.
>
> ------------[ cut here ]------------
> Looking for class "l2tp_sock" with key l2tp_socket_class, but found a different class "slock-AF_INET6" with the same key
> WARNING: CPU: 1 PID: 14195 at kernel/locking/lockdep.c:940 look_up_lock_class+0xcc/0x140
> Modules linked in:
> CPU: 1 PID: 14195 Comm: a.out Not tainted 6.0.0-rc6-dirty #863
> Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
> RIP: 0010:look_up_lock_class+0xcc/0x140
>
> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Urgh, you hitting that WARN enough times to want to improve it seems to
suggest your machine is quite sick.
Anyway, patch is ok I suppose.
next prev parent reply other threads:[~2022-09-19 10:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 15:01 [PATCH] " Tetsuo Handa
2022-09-18 18:31 ` Boqun Feng
2022-09-19 0:52 ` [PATCH v2] " Tetsuo Handa
2022-09-19 10:48 ` Peter Zijlstra [this message]
2022-09-19 13:44 ` Tetsuo Handa
2022-09-21 8:01 ` [tip: locking/core] locking/lockdep: Print more debug information - " tip-bot2 for Tetsuo Handa
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=YyhI93taOenZMHrY@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=will@kernel.org \
/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®