[an error occurred while processing this directive]
|
|
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=whfrTfVMDjgM2fzPjUJpP7y27OsBssZSSCSR7V-=cd1eA@mail.gmail.com>
Date: Tue, 29 Jul 2025 15:11:50 -0700
From: Linus Torvalds <torvalds@...uxfoundation.org>
To: Borislav Petkov <bp@...en8.de>
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, 29 Jul 2025 at 14:52, Borislav Petkov <bp@...en8.de> wrote:
>
> I triggered the same thing today with:
>
> $ gcc-13 --version
> gcc-13 (Debian 13.2.0-25) 13.2.0
Bah. I should have connected the dots and looked at my own compiler
version, because I saw a variation of this same thing yesterday that
caused
section mismatch in reference: volume_set_software_mute+0x6f
(section: .text.unlikely) -> tpacpi_is_lenovo (section: .init.text)
due to gcc not inlining a single-instruction function.
And yes, KCOV was part of it.
And I have gcc version 15.1.1, so clearly "upgrade gcc" isn't the answer.
> I'm thinking if this has worked before, then it must be something coming in
> during the merge window...
The thing that triggered it is apparently commit 381a38ea53d2
("init.h: Disable sanitizer coverage for __init and __head")
Which is supposed to _lessen_ the sanitizer coverage by adding the
__attribute__((no_sanitize("coverage"))), but it's clearly causing
more problems and making gcc just do crazy things.
Linus
Powered by blists - more mailing lists