linux-kernel - Re: [PATCH v2] locking/local_lock: s/l/__l/ and s/tl/_

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] [day] [month] [year] [list]

Message-ID: <20250930064136.c_4utjiu@linutronix.de>
Date: Tue, 30 Sep 2025 08:41:36 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Vincent Mailhol <mailhol@...nel.org>
Cc: Vlastimil Babka <vbabka@...e.cz>, Shakeel Butt <shakeel.butt@...ux.dev>,
	Alexei Starovoitov <ast@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...hat.com>, Will Deacon <will@...nel.org>,
	Waiman Long <longman@...hat.com>, Boqun Feng <boqun.feng@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] locking/local_lock: s/l/__l/ and s/tl/__tl/ to reduce
 risk of shadowing

On 2025-09-29 17:50:47 [+0900], Vincent Mailhol wrote:
> On 9/26/25 11:16 PM, Vlastimil Babka wrote:
> > +CC LOCKING PRIMITIVES maintainers. Looks like local_lock files were never
> > added to the section, should we?
> 
> Shall I resend with the correct list of persons in CC? Or is it OK as-is?

I think you you got them. I didn't have the time to look at this yet.

> Yours sincerely,
> Vincent Mailhol

Sebastian