From: Kees Cook <kees@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org
Cc: Nathan Chancellor <nathan@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>, Sam James <sam@gentoo.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
stable@vger.kernel.org,
Kostadin Shishmanov <kostadinshishmanov@protonmail.com>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH 0/2] A couple of build fixes for x86 when using GCC 15
Date: Thu, 30 Jan 2025 08:07:30 -0800 [thread overview]
Message-ID: <202501300804.20D8CC2@keescook> (raw)
In-Reply-To: <20250121-x86-use-std-consistently-gcc-15-v1-0-8ab0acf645cb@kernel.org>
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. :)
-Kees
> [1]: https://lore.kernel.org/4OAhbllK7x4QJGpZjkYjtBYNLd_2whHx9oFiuZcGwtVR4hIzvduultkgfAIRZI3vQpZylu7Gl929HaYFRGeMEalWCpeMzCIIhLxxRhq4U-Y=@protonmail.com/
> [2]: https://lore.kernel.org/Z4467umXR2PZ0M1H@tucnak/
>
> ---
> Nathan Chancellor (2):
> x86/boot: Use '-std=gnu11' to fix build with GCC 15
> efi: libstub: Use '-std=gnu11' to fix build with GCC 15
>
> arch/x86/boot/compressed/Makefile | 1 +
> drivers/firmware/efi/libstub/Makefile | 2 +-
> 2 files changed, 2 insertions(+), 1 deletion(-)
> ---
> base-commit: ffd294d346d185b70e28b1a28abe367bbfe53c04
> change-id: 20250121-x86-use-std-consistently-gcc-15-f95146e0050f
>
> Best regards,
> --
> Nathan Chancellor <nathan@kernel.org>
>
--
Kees Cook
next prev parent reply other threads:[~2025-01-30 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 1:11 [PATCH 0/2] A couple of build fixes for x86 when using GCC 15 Nathan Chancellor
2025-01-22 1:11 ` [PATCH 1/2] x86/boot: Use '-std=gnu11' to fix build with " Nathan Chancellor
2025-01-29 8:43 ` Ard Biesheuvel
2025-01-22 1:11 ` [PATCH 2/2] efi: libstub: " Nathan Chancellor
2025-01-22 11:56 ` Ard Biesheuvel
2025-01-30 16:07 ` Kees Cook [this message]
2025-01-30 16:20 ` [PATCH 0/2] A couple of build fixes for x86 when using " Ard Biesheuvel
2025-01-30 18:14 ` Dave Hansen
2025-02-22 12:51 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202501300804.20D8CC2@keescook \
--to=kees@kernel.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=jakub@redhat.com \
--cc=kostadinshishmanov@protonmail.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mingo@redhat.com \
--cc=nathan@kernel.org \
--cc=sam@gentoo.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox