linux-kernel - Re: Clarifying confusion of our variable placement rules caused by cleanup.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 for Android: free password hash cracker in your pocket

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

Message-ID: <00a4e7b8-f292-440a-9c08-df802fd52d81@zytor.com>
Date: Tue, 18 Nov 2025 11:19:29 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Bart Van Assche <bvanassche@....org>,
        James Bottomley <James.Bottomley@...senpartnership.com>,
        ksummit@...ts.linux.dev, Dan Williams <dan.j.williams@...el.com>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Dan Carpenter <dan.carpenter@...aro.org>
Subject: Re: Clarifying confusion of our variable placement rules caused by
 cleanup.h

On 2025-11-18 11:16, Linus Torvalds wrote:
> On Tue, 18 Nov 2025 at 11:11, H. Peter Anvin <hpa@...or.com> wrote:
>>
>> Do you want me to send you the patchset during the merge window?
> 
> Sure. I don't think it's a high priority, but I do think it's an
> improvement and allows people to write clearer code.
> 
> I assume all the conversions got acked?
> 

I think so, and most importantly, the only one which wasn't mechanical (at the
maintainer's request.)

However, as long as the actual definition patch gets in there any subsequent
conversions can also go through maintainer trees if they prefer.

	-hpa