From: Greg KH <gregkh@linuxfoundation.org>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Ingo Saitz <ingo@hannover.ccc.de>,
1104745@bugs.debian.org, stable@vger.kernel.org
Subject: Re: Bug#1104745: gcc-15 ICE compiling linux kernel 6.14.5 with CONFIG_RANDSTRUCT
Date: Mon, 23 Jun 2025 10:22:51 +0200 [thread overview]
Message-ID: <2025062341-wrought-work-fbf3@gregkh> (raw)
In-Reply-To: <snq7vjlketwasar4jdufnoostk7xm7umdm6y2xao4tmi4653pd@d6uemvag32nj>
On Wed, Jun 11, 2025 at 06:40:48PM +0200, Uwe Kleine-König wrote:
> Hello Greg, hello Ingo,
>
> On Sun, Jun 08, 2025 at 10:25:50AM +0200, Ingo Saitz wrote:
> > On Wed, Jun 04, 2025 at 10:43:11PM +0200, Uwe Kleine-König wrote:
> > > Control: tag -1 + fixed-upstream
> > > Control: forwarded -1 https://lore.kernel.org/r/20250530221824.work.623-kees@kernel.org
> > >
> > > Hello,
> > >
> > > On Mon, May 05, 2025 at 05:40:57PM +0200, Ingo Saitz wrote:
> > > > When compiling the linux kernel (tested on 6.15-rc5 and 6.14.5 from
> > > > kernel.org) with CONFIG_RANDSTRUCT enabled, gcc-15 throws an ICE:
> > > >
> > > > arch/x86/kernel/cpu/proc.c:174:14: internal compiler error: in comptypes_check_enum_int, at c/c-typeck.cc:1516
> > > > 174 | const struct seq_operations cpuinfo_op = {
> > > > | ^~~~~~~~~~~~~~
> > >
> > > This is claimed to be fixed in upstream by commit
> > > https://git.kernel.org/linus/f39f18f3c3531aa802b58a20d39d96e82eb96c14
> > > that is scheduled to be included in 6.16-rc1.
> >
> > I can confirm applying the patches
> >
> > e136a4062174a9a8d1c1447ca040ea81accfa6a8: randstruct: gcc-plugin: Remove bogus void member
> > f39f18f3c3531aa802b58a20d39d96e82eb96c14: randstruct: gcc-plugin: Fix attribute addition
> >
> > fixes the compile issue (on vanilla 6.12, 6.14 and 6.15 kernel trees;
> > the kernels seem to run fine, too, so far). The first patch was needed
> > for the second to apply cleanly. But I can try to backport only
> > f39f18f3c3531aa802b58a20d39d96e82eb96c14 and see if it still compiles.
>
> @Ingo: Thanks for testing and confirming the backport works.
>
> @gregkh: I think it's reasonable to backport both
> e136a4062174a9a8d1c1447ca040ea81accfa6a8 and
> f39f18f3c3531aa802b58a20d39d96e82eb96c14. Do you already have these on
> your radar?
They are in the stable queues now.
thanks,
greg k-h
prev parent reply other threads:[~2025-06-23 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <174645965734.16657.5032027654487191240.reportbug@spatz.zoo>
2025-06-04 20:43 ` Bug#1104745: gcc-15 ICE compiling linux kernel 6.14.5 with CONFIG_RANDSTRUCT Uwe Kleine-König
2025-06-05 8:43 ` Greg KH
2025-06-08 8:25 ` Ingo Saitz
2025-06-11 16:40 ` Uwe Kleine-König
2025-06-23 8:22 ` Greg KH [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=2025062341-wrought-work-fbf3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=1104745@bugs.debian.org \
--cc=ingo@hannover.ccc.de \
--cc=stable@vger.kernel.org \
--cc=u.kleine-koenig@baylibre.com \
/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