[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z7nIbng2JHSg9in_@gmail.com>
Date: Sat, 22 Feb 2025 13:51:58 +0100
From: Ingo Molnar <mingo@...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>,
Ard Biesheuvel <ardb@...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
* 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. :)
Just an update, the x86 fix is now upstream via:
ee2ab467bddf ("x86/boot: Use '-std=gnu11' to fix build with GCC 15")
Thanks,
Ingo
Powered by blists - more mailing lists