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-next>] [day] [month] [year] [list]
Message-ID: <20250513164807.51780-1-spasswolf@web.de>
Date: Tue, 13 May 2025 18:48:04 +0200
From: Bert Karwatzki <spasswolf@....de>
To: linux-kernel@...r.kernel.org
Cc: Bert Karwatzki <spasswolf@....de>,
	linux-next@...r.kernel.org,
	llvm@...ts.linux.dev,
	Johannes Berg <johannes.berg@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: lockup and kernel panic in linux-next-202505{09,12} when compiled with clang

> 
> I'll now start a bisection where I revert 76a853f86c97 where possible in
> order to find the remaining bugs.
>

The second bisection (from v6.15-rc6 to next-20250512) is finished now:

This commit leads to lockups and kernel panics after
watching ~5-10min of a youtube video while compiling a kernel,
reverting it in next-20250512 is possible:
76a853f86c97 ("wifi: free SKBTX_WIFI_STATUS skb tx_flags flag")
This commit leads to the boot failure, reverting leads to the
compile error it is supposed to fix:
97f4b999e0c8 ("genirq: Use scoped_guard() to shut clang up")

So are these kernel bugs or a clang bugs?

Bert Karwatzki


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ