All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Kees Cook <kees@kernel.org>
Cc: 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, 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: Sat, 22 Feb 2025 13:51:58 +0100	[thread overview]
Message-ID: <Z7nIbng2JHSg9in_@gmail.com> (raw)
In-Reply-To: <202501300804.20D8CC2@keescook>


* Kees Cook <kees@kernel.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


      parent reply	other threads:[~2025-02-22 12:52 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 ` [PATCH 0/2] A couple of build fixes for x86 when using " Kees Cook
2025-01-30 16:20   ` Ard Biesheuvel
2025-01-30 18:14   ` Dave Hansen
2025-02-22 12:51   ` Ingo Molnar [this message]

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=Z7nIbng2JHSg9in_@gmail.com \
    --to=mingo@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=kees@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.