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: <FCFB0721-4A4C-47AF-80DA-A514AB3B0502@zytor.com>
Date: Tue, 06 May 2025 17:31:16 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
CC: Uros Bizjak <ubizjak@...il.com>, x86@...nel.org,
        linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...nel.org>, Borislav Petkov <bp@...en8.de>,
        Dave Hansen <dave.hansen@...ux.intel.com>
Subject: Re: [PATCH -tip 1/3] x86/asm/32: Modernize memset() functions

On May 6, 2025 11:22:49 AM PDT, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>On Tue, 6 May 2025 at 10:55, H. Peter Anvin <hpa@...or.com> wrote:
>>
>> Can anyone think of a reason why we don't do:
>>
>> #define auto __auto_type
>>
>> ... and just start using the modern keyword right away?
>
>Yeah, make it so. The original 'auto' was useless as you say, and
>afaik we've never used it in the kernel.
>
>And the one advantage of it being that historically useless keyword is
>that we can't have variables called 'auto' anywhere either.
>
>So it should be a safe thing to do.
>
>              Linus

Ok, I'll cook up a patchset. Should be trivial.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ