[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <90be9512-2c27-431a-8387-4f2156aa6cb8@intel.com>
Date: Thu, 30 Jan 2025 10:14:56 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Kees Cook <kees@...nel.org>, 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
Cc: 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
On 1/30/25 08:07, Kees Cook 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. 🙂
Thanks for the heads up. It's in here now:
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/log/?h=x86/urgent
Powered by blists - more mailing lists