[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250729215228.GEaIlCnHzcYmGpiBrQ@fat_crate.local>
Date: Tue, 29 Jul 2025 23:52:28 +0200
From: Borislav Petkov <bp@...en8.de>
To: Linus Torvalds <torvalds@...uxfoundation.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
syzbot <syzbot+5245cb609175fb6e8122@...kaller.appspotmail.com>,
dave.hansen@...ux.intel.com, hpa@...or.com,
linux-kernel@...r.kernel.org, mingo@...hat.com,
syzkaller-bugs@...glegroups.com, x86@...nel.org,
Kees Cook <kees@...nel.org>
Subject: Re: [syzbot] upstream build error (23)
On Tue, Jul 29, 2025 at 02:38:50PM -0700, Linus Torvalds wrote:
> I'd personally be perfectly happy just saying "gcc-13 is required" and
> presumably that allows just removing the NOINSTR_HACK thing too.
>
> But I would want somebody to test that and verify that gcc-13 really does do ok.
I was just typing a reply to tglx and saw your mail snow in...
So:
I triggered the same thing today with:
$ gcc-13 --version
gcc-13 (Debian 13.2.0-25) 13.2.0
And with
gcc (Debian 13.3.0-15) 13.3.0
on the other machine.
I'm thinking if this has worked before, then it must be something coming in
during the merge window...
Because 6.16 with the same compiler and kernel builds fine!
So it is something during the merge window *plus* gcc-13!
Your current master which fails with gcc-13 here builds fine with:
gcc (Debian 14.2.0-16) 14.2.0
Copyright (C) 2024 Free Software Foundation, Inc.
I'll run those again tomorrow on a clear head to confirm but it sure sounds
more nasty than just gcc-13 is fine.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists