linux-kernel - Re: next-20250407: qemu_x86_64 clang-20, clang-nightly no console log but gcc-13 boot pass

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Z_QPuPmtrFOnhjeP@gmail.com>
Date: Mon, 7 Apr 2025 19:47:36 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Ard Biesheuvel <ardb@...nel.org>
Cc: Naresh Kamboju <naresh.kamboju@...aro.org>,
	open list <linux-kernel@...r.kernel.org>,
	clang-built-linux <llvm@...ts.linux.dev>,
	Linux Regressions <regressions@...ts.linux.dev>,
	lkft-triage@...ts.linaro.org, Nathan Chancellor <nathan@...nel.org>,
	Dan Carpenter <dan.carpenter@...aro.org>,
	Arnd Bergmann <arnd@...db.de>,
	Anders Roxell <anders.roxell@...aro.org>, dwmw@...zon.co.uk,
	"H. Peter Anvin" <hpa@...or.com>, Kees Cook <keescook@...omium.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: next-20250407: qemu_x86_64 clang-20, clang-nightly no console
 log but gcc-13 boot pass


* Ard Biesheuvel <ardb@...nel.org> wrote:

> On Mon, 7 Apr 2025 at 18:17, Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
> >
> > On Mon, 7 Apr 2025 at 17:15, Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
> > >
> > > Regressions on qemu-x86_64 with clang-20 and clang-nightly on the
> > > Linux next-20250407 and no console output.
> > >
> > > The gcc-13 builds boot pass on qemu-x86_64.
> > >
> > > First seen on the next-20250407.
> > > Bad: next-20250407
> > > Good:next-20250404
> > >
> > > * qemu-x86_64, boot
> > >  - boot/clang-20-lkftconfig
> > >  - boot/clang-20-lkftconfig-compat
> > >  - boot/clang-nightly-lkftconfig
> > >
> > > Regression Analysis:
> > > - New regression? Yes
> > > - Reproducibility? Yes
> > >
> > > Boot regression: qemu_x86_64 clang-20, clang-nightly no console log
> > > Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> >
> > Anders bisected this and found,
> > # first bad commit:
> >    [cc34e658c6db493c1524077e95b42d478de58f2b]
> >    x86/boot: Move the early GDT/IDT setup code into startup/
> >
> > Lore report link,
> >  - https://lore.kernel.org/all/CA+G9fYt4VVa3kUDR+ze05xM+fRmMBVfbBTsypUq5oOpAfuzjfg@mail.gmail.com/
> >
> 
> Thanks for the report. I'll look into this.

I've zapped cc34e658c6db from tip:x86/boot for the time being.

I have the same request as for the other patches applies, please split 
it up into ~3 patches for better bisectability and ease of review:

 - first the mechanic movement of code, with very few changes (if the 
   result builds & boots),

 - then drop the RIP_REL_REF() uses in the second patch,

 - and drop __head annotations in the third patch.

Thanks,

	Ingo