linux-kernel - Re: [PATCH 0/2] A couple of build fixes for x86 when using GCC 15

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: <CAMj1kXH0T5XJGMyC72DQjp0zjTAC5JbtDjY=rDGPeMs6cVDXug@mail.gmail.com>
Date: Thu, 30 Jan 2025 17:20:03 +0100
From: Ard Biesheuvel <ardb@...nel.org>
To: Kees Cook <kees@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>, 
	Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org, 
	Nathan Chancellor <nathan@...nel.org>, Sam James <sam@...too.org>, 
	Masahiro Yamada <masahiroy@...nel.org>, Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org, 
	linux-efi@...r.kernel.org, stable@...r.kernel.org, 
	Kostadin Shishmanov <kostadinshishmanov@...tonmail.com>, Jakub Jelinek <jakub@...hat.com>
Subject: Re: [PATCH 0/2] A couple of build fixes for x86 when using GCC 15

On Thu, 30 Jan 2025 at 17:07, Kees Cook <kees@...nel.org> wrote:
>
> On Tue, Jan 21, 2025 at 06:11:32PM -0700, Nathan Chancellor wrote:
> > GCC 15 changed the default C standard version from gnu17 to gnu23, which
> > reveals a few places in the kernel where a C standard version was not
> > set, resulting in build failures because bool, true, and false are
> > reserved keywords in C23 [1][2]. Update these places to use the same C
> > standard version as the rest of the kernel, gnu11.
>
> Hello x86 maintainers!
>
> I think this would be valuable to get into -rc1 since we're getting very
> close to a GCC 15 release. Can someone get this into -tip urgent,
> please? If everyone is busy I can take it via the hardening tree, as we
> appear to be the ones tripping over it the most currently. :)
>

+1

Note that I already took the EFI one.