linux-kernel - Re: [PATCH] locking/mutex: Redo __mutex

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20251105135425.RJoTs_-A@linutronix.de>
Date: Wed, 5 Nov 2025 14:54:25 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Waiman Long <llong@...hat.com>
Cc: linux-kernel@...r.kernel.org, Boqun Feng <boqun.feng@...il.com>,
	Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Will Deacon <will@...nel.org>
Subject: Re: [PATCH] locking/mutex: Redo __mutex_init()

On 2025-11-05 08:49:05 [-0500], Waiman Long wrote:
> > If you want __mutex_init() for the generic, regardless, we would first
> > need to make room and then something like mutex_init_lockdep() could be
> > the public interface replacing __mutex_init() in its current function.
> 
> Ah, I don't realize that there are users of __mutex_init() outside of the
> locking subsystem. In this case, we have to maintain the semantics of
> __mutex_init() to avoid affecting other subsystems.

Well, we could update them to mutex_init() +
lockdep_set_class_and_name(). Except probably for rust. But still if we
like _generic, we like _generic ;)

> Thanks for the clarification.
> 
> Cheers,
> Longman

Sebastian