From: Heo <tj@kernel.org>
To: 许东洁 <xudongjie25@mails.ucas.ac.cn>
Cc: Zijlstra <peterz@infradead.org>,
Jiangshan <jiangshanlai@gmail.com>, Molnar <mingo@redhat.com>,
Deacon <will@kernel.org>, Feng <boqun.feng@gmail.com>,
Long <longman@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] lockdep: MAX_LOCKDEP_KEYS too low when destroying workqueues
Date: Mon, 1 Dec 2025 19:48:19 -1000 [thread overview]
Message-ID: <aS59o0EE31RLlFb7@slm.duckdns.org> (raw)
In-Reply-To: <34e8a1ee.3323c.19ad4011944.Coremail.xudongjie25@mails.ucas.ac.cn>
On Sun, Nov 30, 2025 at 05:03:53PM +0800, 许东洁 wrote:
> Hello,
>
> I found a lockdep issue using syzkaller where repeatedly destroying workqueues exhausts
> MAX_LOCKDEP_KEYS and disables the lock validator.
>
> The bug triggers through:
> nci_unregister_device -> destroy_workqueue -> drain_workqueue -> touch_wq_lockdep_map
>
> Kernel output:
> BUG: MAX_LOCKOCKDEP_KEYS too low!
> turning off the locking correctness validator.
>
> It appears workqueue lock classes are not properly released in destroy_workqueue,
> causing lock class leakage.
Looks like the repro ends up creating and destroying workqueues back to
back. Part of workqueue destruction is asynchronous, so if you do that
quickly enough, running out of lockdep keys isn't that surprising. I'm not
sure this is a meaningful bug report.
Thanks.
--
tejun
prev parent reply other threads:[~2025-12-02 5:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-30 9:03 许东洁
2025-12-02 5:48 ` Heo [this message]
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=aS59o0EE31RLlFb7@slm.duckdns.org \
--to=tj@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
--cc=xudongjie25@mails.ucas.ac.cn \
/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®