From: Peter Zijlstra <peterz@infradead.org>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: "Alex Gaynor" <alex.gaynor@gmail.com>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Josh Poimboeuf" <jpoimboe@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
rust-for-linux@vger.kernel.org,
"Nathan Chancellor" <nathan@kernel.org>,
"Nicolas Schier" <nicolas@fjasle.eu>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] objtool/rust: add one more `noreturn` Rust function for Rust 1.89.0
Date: Mon, 14 Jul 2025 10:46:38 +0200 [thread overview]
Message-ID: <20250714084638.GL905792@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250712160103.1244945-2-ojeda@kernel.org>
On Sat, Jul 12, 2025 at 06:01:02PM +0200, Miguel Ojeda wrote:
> Starting with Rust 1.89.0 (expected 2025-08-07), under
> `CONFIG_RUST_DEBUG_ASSERTIONS=y`, `objtool` may report:
>
> rust/kernel.o: warning: objtool: _R..._6kernel4pageNtB5_4Page8read_raw()
> falls through to next function _R..._6kernel4pageNtB5_4Page9write_raw()
>
> (and many others) due to calls to the `noreturn` symbol:
>
> core::panicking::panic_nounwind_fmt
>
> Thus add the mangled one to the list so that `objtool` knows it is
> actually `noreturn`.
>
> See commit 56d680dd23c3 ("objtool/rust: list `noreturn` Rust functions")
> for more details.
>
> Cc: stable@vger.kernel.org # Needed in 6.12.y and later (Rust is pinned in older LTSs).
> Cc: Josh Poimboeuf <jpoimboe@kernel.org>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
> tools/objtool/check.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/objtool/check.c b/tools/objtool/check.c
> index f23bdda737aa..3257eefc41ed 100644
> --- a/tools/objtool/check.c
> +++ b/tools/objtool/check.c
> @@ -224,6 +224,7 @@ static bool is_rust_noreturn(const struct symbol *func)
> str_ends_with(func->name, "_4core9panicking14panic_explicit") ||
> str_ends_with(func->name, "_4core9panicking14panic_nounwind") ||
> str_ends_with(func->name, "_4core9panicking18panic_bounds_check") ||
> + str_ends_with(func->name, "_4core9panicking18panic_nounwind_fmt") ||
> str_ends_with(func->name, "_4core9panicking19assert_failed_inner") ||
> str_ends_with(func->name, "_4core9panicking30panic_null_pointer_dereference") ||
> str_ends_with(func->name, "_4core9panicking36panic_misaligned_pointer_dereference") ||
Just having "_4core9panicking" substring is not sufficient?
next prev parent reply other threads:[~2025-07-14 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-12 16:01 [PATCH 0/2] Rust fixes for the upcoming 1.89 release Miguel Ojeda
2025-07-12 16:01 ` [PATCH 1/2] objtool/rust: add one more `noreturn` Rust function for Rust 1.89.0 Miguel Ojeda
2025-07-14 8:46 ` Peter Zijlstra [this message]
2025-07-14 8:48 ` Alice Ryhl
2025-07-14 9:01 ` Peter Zijlstra
2025-07-12 16:01 ` [PATCH 2/2] rust: use `#[used(compiler)]` to fix build and `modpost` with Rust >= 1.89.0 Miguel Ojeda
2025-07-14 8:55 ` Alice Ryhl
2025-07-14 23:38 ` [PATCH 0/2] Rust fixes for the upcoming 1.89 release Miguel Ojeda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250714084638.GL905792@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=jpoimboe@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tmgross@umich.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®