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] [day] [month] [year] [list]
Message-ID: <20250405002757.GA836042@ax162>
Date: Fri, 4 Apr 2025 17:27:57 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: open list <linux-kernel@...r.kernel.org>,
	Linux ARM <linux-arm-kernel@...ts.infradead.org>,
	lkft-triage@...ts.linaro.org,
	Linux Regressions <regressions@...ts.linux.dev>,
	clang-built-linux <llvm@...ts.linux.dev>,
	Arnd Bergmann <arnd@...db.de>, Ard Biesheuvel <ardb@...nel.org>,
	Dan Carpenter <dan.carpenter@...aro.org>,
	Anders Roxell <anders.roxell@...aro.org>
Subject: Re: v6.14-12245-g91e5bfe317d8: Boot regression: rk3399-rock-pi-4b
 dragonboard-410c dragonboard-845c no console output

On Thu, Apr 03, 2025 at 04:17:44PM +0530, Naresh Kamboju wrote:
> I’ve re-run the tests to validate the boot behavior on the Rock Pi 4 board
> with different Clang nightly versions and the latest mainline kernel.
> 
> The combination using clang-nightly:20250319 successfully booted the
> Rock Pi 4 board.
> However, the combination using clang-nightly:20250401 failed to boot
> the same board.
> 
> "name": "clang",
> "version": "21.0.0",
> "version_full": "Debian clang version 21.0.0
> (++20250401112529+290d7b82cb5d-1~exp1~20250401112547.1360)"
> 
> Reference:
>  - https://lkft.validation.linaro.org/scheduler/job/8196258
>  - https://lkft.validation.linaro.org/scheduler/job/8196275

Thank you for verifying. Do you test with clang-20 and if so, are tests
at that same revision passing? I want to make sure this is an LLVM
regression before trying to get into figuring out how to bisect with
your setup. Another way to do that is to see if clang-nightly boots are
failing on the stable branches, which would point to Linux not being at
fault.

Cheers,
Nathan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ