lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANp29Y4cTQD0EB6pTHgbbrja8ExxZuoz+RRLDY1ua+FQ=EjJ9w@mail.gmail.com>
Date: Tue, 29 Jul 2025 16:32:39 +0200
From: Aleksandr Nogikh <nogikh@...gle.com>
To: Borislav Petkov <bp@...en8.de>
Cc: syzbot <syzbot+5245cb609175fb6e8122@...kaller.appspotmail.com>, 
	Ard Biesheuvel <ardb@...nel.org>, dave.hansen@...ux.intel.com, hpa@...or.com, 
	linux-kernel@...r.kernel.org, mingo@...hat.com, 
	syzkaller-bugs@...glegroups.com, tglx@...utronix.de, x86@...nel.org
Subject: Re: [syzbot] upstream build error (23)

On Tue, Jul 29, 2025 at 4:25 PM Borislav Petkov <bp@...en8.de> wrote:
>
> + Ard.
>
> On Tue, Jul 29, 2025 at 06:43:32AM -0700, syzbot wrote:
> > Hello,
> >
> > 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@...kaller.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'
> > ld: arch/x86/kernel/setup.c:971: undefined reference to `efi_memblock_x86_reserve_range'
> > arch/x86/kernel/cpu/mshyperv.c:496: undefined reference to `isolation_type_tdx'
> > ld: arch/x86/kernel/cpu/mshyperv.c:494: undefined reference to `isolation_type_snp'
> > arch/x86/kernel/kvm.c:600: undefined reference to `efi'
> > ld: arch/x86/kernel/kvm.c:600: undefined reference to `efi'
> > drivers/acpi/osl.c:210: undefined reference to `efi'
> > ld: drivers/acpi/osl.c:210: undefined reference to `efi'
>
> # CONFIG_EFI is not set
>
> If that's a random config, why do we care?

It's not a random config - syzbot uses a set of fixed kernel configs
(most without CONFIG_EFI, as in this report) which used to work well
before today.

-- 
Aleksandr

>
> --
> Regards/Gruss,
>     Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ