linux-kernel - Re: Mainline: v6.10-rc6 boot failed across all arm64 devices

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: <20240701124149.GA2095@willie-the-truck>
Date: Mon, 1 Jul 2024 13:41:49 +0100
From: Will Deacon <will@...nel.org>
To: Mark Brown <broonie@...nel.org>
Cc: Naresh Kamboju <naresh.kamboju@...aro.org>,
	Linux ARM <linux-arm-kernel@...ts.infradead.org>,
	open list <linux-kernel@...r.kernel.org>,
	lkft-triage@...ts.linaro.org,
	Linux Regressions <regressions@...ts.linux.dev>,
	Catalin Marinas <catalin.marinas@....com>,
	Mark Rutland <mark.rutland@....com>,
	Aishwarya TCV <Aishwarya.TCV@....com>,
	Arnd Bergmann <arnd@...db.de>,
	Dan Carpenter <dan.carpenter@...aro.org>,
	Anders Roxell <anders.roxell@...aro.org>
Subject: Re: Mainline: v6.10-rc6 boot failed across all arm64 devices

On Mon, Jul 01, 2024 at 01:12:07PM +0100, Mark Brown wrote:
> On Mon, Jul 01, 2024 at 05:28:29PM +0530, Naresh Kamboju wrote:
> > The mainline kernel v6.10-rc6 boot failed across all arm64 devices and
> > qemu-arm64 and no crash log found (earlycon) did not help.
> > 
> > But the defconfig builds boot PASS.
> > 
> > The boot problem is with defconfig + Extra Kconfigs and builds links
> > provided in the bottom of this email.
> > 
> > The boot test history shows that,
> >   GOOD: v6.10-rc5
> >   BAD:  v6.10-rc6
> 
> Other CI systems aren't showing this.  I'm guessing you've updated the
> toolchain versions you're using and are running into:
> 
>    https://sourceware.org/bugzilla/show_bug.cgi?id=31924#c9
> 
> and will see this with other kernels.  It's probably worth testing
> toolchains before deploying them...

Aha, that would explain why I'm failing to reproduce this with clang or
my old version of GCC. I only see the problem with the binary provided
by the CI.

Will