From: Thomas Gleixner <tglx@linutronix.de>
To: syzbot <syzbot+5245cb609175fb6e8122@syzkaller.appspotmail.com>,
bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, mingo@redhat.com,
syzkaller-bugs@googlegroups.com, x86@kernel.org
Cc: Linus Torvalds <torvalds@linuxfoundation.org>
Subject: Re: [syzbot] upstream build error (23)
Date: Tue, 29 Jul 2025 21:36:14 +0200 [thread overview]
Message-ID: <87cy9ikcwh.ffs@tglx> (raw)
In-Reply-To: <6888d004.a00a0220.26d0e1.0004.GAE@google.com>
On Tue, Jul 29 2025 at 06:43, syzbot wrote:
> syzbot found the following issue on:
>
> HEAD commit: 86aa72182095 Merge tag 'chrome-platform-v6.17' of git://gi..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=171674a2580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=3816ffa0a2bab886
> dashboard link: https://syzkaller.appspot.com/bug?extid=5245cb609175fb6e8122
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+5245cb609175fb6e8122@syzkaller.appspotmail.com
>
> arch/x86/kernel/setup.c:1251: undefined reference to `efi_mem_type'
> ld: arch/x86/kernel/setup.c:987: undefined reference to `efi_init'
Cute. So the code has:
if (efi_enabled(EFI_BOOT))
efi_init();
in the CONFIG_EFI=n case:
static inline bool efi_enabled(int feature)
{
return false;
}
efi_init() has an unconditional forward declaration:
extern void efi_init (void);
This has been the case forever and has been optimized out because
efi_enabled() evaluates to a constant.
I haven't checked which sanitizer option causes GCC to compile this
into:
00000000000000d0 <efi_enabled.constprop.0>:
}
extern void efi_find_mirror(void);
#else
static inline bool efi_enabled(int feature)
{
return false;
d0: e8 00 00 00 00 call d5 <efi_enabled.constprop.0+0x5>
}
d5: 31 c0 xor %eax,%eax
d7: e9 00 00 00 00 jmp dc <efi_enabled.constprop.0+0xc>
and to keep the call for efi_init() as a symbol for the linker to
resolve, which obviously fails.
If I change the efi_enabled() stub to __always_inline, it's optimized
out.
Disabling CONFIG_KCOV_INSTRUMENT_ALL makes it go away. So GCC confuses
the optimizer when CONFIG_KCOV_INSTRUMENT_ALL is on.
The kernel is full of such inline (not __always_inline) stub
conditionals which evaluate to a constant....
Thanks,
tglx
next prev parent reply other threads:[~2025-07-29 19:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 13:43 [syzbot] upstream build error (23) syzbot
2025-07-29 14:25 ` Borislav Petkov
2025-07-29 14:32 ` Aleksandr Nogikh
2025-07-29 14:48 ` Borislav Petkov
2025-07-29 19:36 ` Thomas Gleixner [this message]
2025-07-29 21:17 ` Thomas Gleixner
2025-07-29 21:38 ` Linus Torvalds
2025-07-29 21:52 ` Borislav Petkov
2025-07-29 22:11 ` Linus Torvalds
2025-07-29 22:27 ` Kees Cook
2025-07-29 22:12 ` Kees Cook
2025-07-30 10:44 ` Thomas Gleixner
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=87cy9ikcwh.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=syzbot+5245cb609175fb6e8122@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linuxfoundation.org \
--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