linux-kernel - Re: [PATCH 1/2] locking/mutex: Clean up mutex.h

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]

Date: Mon, 12 Feb 2024 02:28:13 +0300
From: George Stark <gnstark@...utedevices.com>
To: Waiman Long <longman@...hat.com>, Peter Zijlstra <peterz@...radead.org>,
	Boqun Feng <boqun.feng@...il.com>, Will Deacon <will@...nel.org>, Ingo Molnar
	<mingo@...hat.com>, Andrew Morton <akpm@...ux-foundation.org>
CC: <gregkh@...uxfoundation.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "kernel@...utedevices.com"
	<kernel@...utedevices.com>
Subject: Re: [PATCH 1/2] locking/mutex: Clean up mutex.h

Hello

Excuse me, this is my 4th letter here since December 2023 and there's no 
response unfortunately.

Just to recall that we had the discussion in December 2023 about 
implementing devm_mutex_init. We came to conclusion that the only 
effective way to do it in include/linux/mutex.h but mutex.h requires
some cleanups to simplify the devm_mutex_init patch.
mutex.h owners proposed such a cleanup patch themselves and there's no 
progress since that. How can we move forward on those patches?

Cleanup patch:
https://lore.kernel.org/lkml/20231216013656.1382213-1-longman@redhat.com/

Original problem that requires devm_mutex_init and discussion:
https://lore.kernel.org/lkml/ZcZeRmVjEPhVPW9-@smile.fi.intel.com/T/#m0f514f8f96e18db9568f84b2df37aaf648874a4a

-- 
Best regards
George