From: Waiman Long <llong@redhat.com>
To: Boqun Feng <boqun.feng@gmail.com>, Nathan Chancellor <nathan@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Waiman Long <llong@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>, Will Deacon <will@kernel.org>
Subject: Re: linux-next: boot warning from the final tree
Date: Sat, 22 Nov 2025 19:50:03 -0500 [thread overview]
Message-ID: <aa36e8b8-5e78-4329-9813-75ae46d3417a@redhat.com> (raw)
In-Reply-To: <aSDoquGlA55Ge100@tardis.local>
On 11/21/25 5:33 PM, Boqun Feng wrote:
> Subject: [PATCH] locking/mutex: Initialize mutex::magic even when LOCKDEP=n
>
> When DEBUG_MUTEXES=y and LOCKDEP=n, mutex_lock() still checks on
> ->magic, hence debug_mutex_init() should be called in
> mutex_init_generic() as well. While we are at it, decouple LOCKDEP
> logic from debug_mutex_init(), because in this way debug_mutex_init()
> only needs one parameter, and we now have mutex_init_lockep() for
> LOCKDEP=y scenarios.
>
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Closes: https://lore.kernel.org/lkml/20251117202214.4f710f02@canb.auug.org.au/
> Reported-by: Nathan Chancellor <nathan@kernel.org>
> Closes: https://lore.kernel.org/lkml/20251121215819.GA1374726@ax162/
> Fixes: 3572e2edc7b6 ("locking/mutex: Redo __mutex_init()")
> Signed-off-by: Boqun Feng <boqun.feng@gmail.com>
> ---
> kernel/locking/mutex-debug.c | 10 +---------
> kernel/locking/mutex.c | 8 +++++++-
> kernel/locking/mutex.h | 5 ++---
> 3 files changed, 10 insertions(+), 13 deletions(-)
>
> diff --git a/kernel/locking/mutex-debug.c b/kernel/locking/mutex-debug.c
> index 949103fd8e9b..2c6b02d4699b 100644
> --- a/kernel/locking/mutex-debug.c
> +++ b/kernel/locking/mutex-debug.c
> @@ -78,16 +78,8 @@ void debug_mutex_unlock(struct mutex *lock)
> }
> }
>
> -void debug_mutex_init(struct mutex *lock, const char *name,
> - struct lock_class_key *key)
> +void debug_mutex_init(struct mutex *lock)
> {
> -#ifdef CONFIG_DEBUG_LOCK_ALLOC
> - /*
> - * Make sure we are not reinitializing a held lock:
> - */
> - debug_check_no_locks_freed((void *)lock, sizeof(*lock));
> - lockdep_init_map_wait(&lock->dep_map, name, key, 0, LD_WAIT_SLEEP);
> -#endif
> lock->magic = lock;
> }
>
> diff --git a/kernel/locking/mutex.c b/kernel/locking/mutex.c
> index f3bb352a368d..2a1d165b3167 100644
> --- a/kernel/locking/mutex.c
> +++ b/kernel/locking/mutex.c
> @@ -51,6 +51,7 @@ static void __mutex_init_generic(struct mutex *lock)
> #ifdef CONFIG_MUTEX_SPIN_ON_OWNER
> osq_lock_init(&lock->osq);
> #endif
> + debug_mutex_init(lock);
> }
>
> static inline struct task_struct *__owner_task(unsigned long owner)
> @@ -173,7 +174,12 @@ static __always_inline bool __mutex_unlock_fast(struct mutex *lock)
> void mutex_init_lockep(struct mutex *lock, const char *name, struct lock_class_key *key)
> {
> __mutex_init_generic(lock);
> - debug_mutex_init(lock, name, key);
> +
> + /*
> + * Make sure we are not reinitializing a held lock:
> + */
> + debug_check_no_locks_freed((void *)lock, sizeof(*lock));
> + lockdep_init_map_wait(&lock->dep_map, name, key, 0, LD_WAIT_SLEEP);
> }
> EXPORT_SYMBOL(mutex_init_lockep);
> #endif /* !CONFIG_DEBUG_LOCK_ALLOC */
> diff --git a/kernel/locking/mutex.h b/kernel/locking/mutex.h
> index 2e8080a9bee3..9ad4da8cea00 100644
> --- a/kernel/locking/mutex.h
> +++ b/kernel/locking/mutex.h
> @@ -59,8 +59,7 @@ extern void debug_mutex_add_waiter(struct mutex *lock,
> extern void debug_mutex_remove_waiter(struct mutex *lock, struct mutex_waiter *waiter,
> struct task_struct *task);
> extern void debug_mutex_unlock(struct mutex *lock);
> -extern void debug_mutex_init(struct mutex *lock, const char *name,
> - struct lock_class_key *key);
> +extern void debug_mutex_init(struct mutex *lock);
> #else /* CONFIG_DEBUG_MUTEXES */
> # define debug_mutex_lock_common(lock, waiter) do { } while (0)
> # define debug_mutex_wake_waiter(lock, waiter) do { } while (0)
> @@ -68,6 +67,6 @@ extern void debug_mutex_init(struct mutex *lock, const char *name,
> # define debug_mutex_add_waiter(lock, waiter, ti) do { } while (0)
> # define debug_mutex_remove_waiter(lock, waiter, ti) do { } while (0)
> # define debug_mutex_unlock(lock) do { } while (0)
> -# define debug_mutex_init(lock, name, key) do { } while (0)
> +# define debug_mutex_init(lock) do { } while (0)
> #endif /* !CONFIG_DEBUG_MUTEXES */
> #endif /* CONFIG_PREEMPT_RT */
Reviewed-by: Waiman Long <longman@redhat.com>
next prev parent reply other threads:[~2025-11-23 0:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 9:22 linux-next: boot warning from the final tree Stephen Rothwell
2025-11-21 21:58 ` Nathan Chancellor
2025-11-21 22:33 ` Boqun Feng
2025-11-22 7:37 ` Nathan Chancellor
2025-11-23 0:50 ` Waiman Long [this message]
2025-11-24 7:45 ` Sebastian Andrzej Siewior
2025-11-25 14:54 ` [PATCH] locking/mutex: Initialize mutex::magic even when LOCKDEP=n Boqun Feng
2025-11-28 5:08 ` Stephen Rothwell
2025-11-28 9:55 ` Peter Zijlstra
2025-11-28 10:29 ` Stephen Rothwell
2025-11-28 9:36 ` Peter Zijlstra
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=aa36e8b8-5e78-4329-9813-75ae46d3417a@redhat.com \
--to=llong@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nathan@kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--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