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: <20250114171816.GA3416405@ax162>
Date: Tue, 14 Jan 2025 10:18:16 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Klaus Kusche <klaus.kusche@...puterix.info>,
	Josh Poimboeuf <jpoimboe@...nel.org>
Cc: peterz@...radead.org, linux-kernel@...r.kernel.org,
	llvm@...ts.linux.dev, Nick Desaulniers <ndesaulniers@...gle.com>
Subject: Re: "Bad or missing .orc_unwind table. Disabling unwinder." Clang 19
 problem? 6.12.8 problem?

On Tue, Jan 14, 2025 at 10:59:44AM +0100, Klaus Kusche wrote:
> On 14/01/2025 10:51, Nathan Chancellor wrote:
> >> Nathan, I think this is a Clang 19 issue, where one of the jump table
> >> entries is pointing past the end of the function.  When we saw this in
> >> the past I think it was due to some leftover optimization, where the
> >> jump table entry ended up unused so it was harmless.  Are you aware of
> >> any recent bugs in that area?
> > 
> > I am not aware of any recent bugs there but if you or Klaus have a
> > configuration file that triggers this, I would be happy to bisect LLVM
> > to see what change introduced it to give us a better understanding of
> > what is happening here.
> 
> Kernel .config files are attached to both
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=219685
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=219686

Thanks a lot, I missed that since I do not interact with Bugzilla much.

I bisected this change in behavior to LLVM commit 64ed699b3d81 ("Reland
"[SimplifyCFG] When only one case value is missing, replace default with
that case (#76669)"") [1]. I can see how that would cause this issue but
I am not sure how it is specifically interacting with this particular
kernel code. I am going to try and tease out a reproducer for this and
report it upstream but it would still probably be good to consider if
objtool could handle this, especially in the face of the upcoming
--Werror.

[1]: https://github.com/llvm/llvm-project/commit/64ed699b3d811407e5a9f1111f63e11dc7f7dd80

Cheers,
Nathan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ