From: Bart Van Assche <bvanassche@acm.org>
To: Nilay Shroff <nilay@linux.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Boqun Feng <boqun@kernel.org>, Waiman Long <longman@redhat.com>,
linux-kernel@vger.kernel.org
Cc: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Geliang Tang <geliang@kernel.org>
Subject: Re: [PATCH v2] lockdep: Fix subclass resource leak in lockdep_unregister_key()
Date: Mon, 27 Jul 2026 12:51:19 -0700 [thread overview]
Message-ID: <4ad8d6eb-aa40-44cc-b72d-60cccf590809@acm.org> (raw)
In-Reply-To: <20260727182312.3750145-1-nilay@linux.ibm.com>
On 7/27/26 11:23 AM, Nilay Shroff wrote:
> Fix this by instructing lockdep_unregister_key() to look ahead across
> the entire valid subclass allocation block range
> (MAX_LOCKDEP_SUBCLASSES), ensuring that all related subclass matrix
> definitions are completely zapped alongside the primary key.
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
prev parent reply other threads:[~2026-07-27 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 18:23 Nilay Shroff
2026-07-27 19:51 ` Bart Van Assche [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=4ad8d6eb-aa40-44cc-b72d-60cccf590809@acm.org \
--to=bvanassche@acm.org \
--cc=boqun@kernel.org \
--cc=geliang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=nilay@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=shinichiro.kawasaki@wdc.com \
--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®