public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boqun Feng <boqun.feng@gmail.com>
To: Waiman Long <llong@redhat.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Will Deacon <will@kernel.org>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] locking: lockdep: Decrease nr_unused_locks if lock unused in zap_class()
Date: Wed, 26 Mar 2025 11:31:19 -0700	[thread overview]
Message-ID: <67e447f9.c80a0220.d7401.34ce@mx.google.com> (raw)
In-Reply-To: <5f02cf04-74bf-46e5-8104-a62d4aca2bfd@redhat.com>

On Wed, Mar 26, 2025 at 02:26:53PM -0400, Waiman Long wrote:
> 
> On 3/26/25 2:08 PM, Boqun Feng wrote:
> > Currently, when a lock class is allocated, nr_unused_locks will be
> > increased by 1, until it gets used: nr_unused_locks will be decreased by
> > 1 in mark_lock(). However, one scenario is missed: a lock class may be
> > zapped without even being used once. This could result into a situation
> > that nr_unused_locks != 0 but no unused lock class is active in the
> > system, and when `cat /proc/lockdep_stats`, a WARN_ON() will
> > be triggered in a CONFIG_DEBUG_LOCKDEP=y kernel:
> > 
> > [...] DEBUG_LOCKS_WARN_ON(debug_atomic_read(nr_unused_locks) != nr_unused)
> > [...] WARNING: CPU: 41 PID: 1121 at kernel/locking/lockdep_proc.c:283 lockdep_stats_show+0xba9/0xbd0
> > 
> > And as a result, lockdep will be disabled after this.
> > 
> > Therefore, nr_unused_locks needs to be accounted correctly at
> > zap_class() time.
> > 
> > Cc: stable@vger.kernel.org
> > Signee-off-by: Boqun Feng <boqun.feng@gmail.com>
> 
> Typo: "Signee-off-by"?
> 

Oops, yeah.

> Other than that, LGTM
> 
> Reviewed-by: Waiman Long <longman@redhat.com>
> 

Thanks!

Regards,
Boqun

> > ---
> >   kernel/locking/lockdep.c | 3 +++
> >   1 file changed, 3 insertions(+)
> > 
> > diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
> > index b15757e63626..686546d52337 100644
> > --- a/kernel/locking/lockdep.c
> > +++ b/kernel/locking/lockdep.c
> > @@ -6264,6 +6264,9 @@ static void zap_class(struct pending_free *pf, struct lock_class *class)
> >   		hlist_del_rcu(&class->hash_entry);
> >   		WRITE_ONCE(class->key, NULL);
> >   		WRITE_ONCE(class->name, NULL);
> > +		/* class allocated but not used, -1 in nr_unused_locks */
> > +		if (class->usage_mask == 0)
> > +			debug_atomic_dec(nr_unused_locks);
> >   		nr_lock_classes--;
> >   		__clear_bit(class - lock_classes, lock_classes_in_use);
> >   		if (class - lock_classes == max_lock_class_idx)
> 

  reply	other threads:[~2025-03-26 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 18:08 [PATCH] locking: lockdep: Decrease nr_unused_locks if lock unused in zap_class() Boqun Feng
2025-03-26 18:26 ` Waiman Long
2025-03-26 18:31   ` Boqun Feng [this message]
2025-03-27  7:24 ` Ingo Molnar
2025-03-27  7:29 ` [tip: locking/urgent] locking/lockdep: " tip-bot2 for Boqun Feng

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=67e447f9.c80a0220.d7401.34ce@mx.google.com \
    --to=boqun.feng@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llong@redhat.com \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=stable@vger.kernel.org \
    --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