linux-kernel - Re: [PATCH 1/5] objtool/rust: add one more `noreturn` Rust function for Rust 1.87.0

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: <554965650ac2aaa210028d495b06e1ede6aab74d.camel@nvidia.com>
Date: Wed, 14 May 2025 19:46:49 +0000
From: Timur Tabi <ttabi@...dia.com>
To: Joel Fernandes <joelagnelf@...dia.com>, "jpoimboe@...nel.org"
	<jpoimboe@...nel.org>
CC: "gary@...yguo.net" <gary@...yguo.net>, "a.hindborg@...nel.org"
	<a.hindborg@...nel.org>, "ojeda@...nel.org" <ojeda@...nel.org>,
	"boqun.feng@...il.com" <boqun.feng@...il.com>, "patches@...ts.linux.dev"
	<patches@...ts.linux.dev>, "stable@...r.kernel.org" <stable@...r.kernel.org>,
	"tmgross@...ch.edu" <tmgross@...ch.edu>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "alex.gaynor@...il.com"
	<alex.gaynor@...il.com>, "benno.lossin@...ton.me" <benno.lossin@...ton.me>,
	John Hubbard <jhubbard@...dia.com>, "rust-for-linux@...r.kernel.org"
	<rust-for-linux@...r.kernel.org>, "bjorn3_gh@...tonmail.com"
	<bjorn3_gh@...tonmail.com>, "peterz@...radead.org" <peterz@...radead.org>,
	"aliceryhl@...gle.com" <aliceryhl@...gle.com>, Alexandre Courbot
	<acourbot@...dia.com>, "dakr@...nel.org" <dakr@...nel.org>, Alistair Popple
	<apopple@...dia.com>
Subject: Re: [PATCH 1/5] objtool/rust: add one more `noreturn` Rust function
 for Rust 1.87.0

On Wed, 2025-05-14 at 12:14 -0700, Josh Poimboeuf wrote:
> The above warning is in completely different code from the Rust one, so
> they're likely unrelated.

True, but the fall-through is bogus in the C code as well.

> The fallthrough warnings are typically caused by either Clang undefined
> behavior (usually potential divide by zero or negative shift), or a call
> to an unannotated noreturn function.
> 
> Timur, can you share your .config and compiler version?

.config: https://pastebin.com/inDHfmbG

ttabi@...bi:~$ llvm-config --version
18.1.3
ttabi@...bi:~$ gcc --version
gcc (Ubuntu 14.2.0-4ubuntu2~24.04) 14.2.0

Since I build with LLVM=1, I'm assuming the answer is 18.1.3