aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/drivers/net/lib/py/remote_ssh.py
diff options
context:
space:
mode:
authorMiguel Ojeda <[email protected]>2025-05-02 14:02:33 +0000
committerMiguel Ojeda <[email protected]>2025-05-06 22:08:51 +0000
commit19f5ca461d5fc09bdf93a9f8e4bd78ed3a49dc71 (patch)
tree56222adfb52642c1380ea4b7c7f1c5d3c74e1e6d /tools/testing/selftests/drivers/net/lib/py/remote_ssh.py
parentLinux 6.15-rc5 (diff)
downloadkernel-19f5ca461d5fc09bdf93a9f8e4bd78ed3a49dc71.tar.gz
kernel-19f5ca461d5fc09bdf93a9f8e4bd78ed3a49dc71.zip
objtool/rust: add one more `noreturn` Rust function for Rust 1.87.0
Starting with Rust 1.87.0 (expected 2025-05-15), `objtool` may report: rust/core.o: warning: objtool: _R..._4core9panicking9panic_fmt() falls through to next function _R..._4core9panicking18panic_nounwind_fmt() rust/core.o: warning: objtool: _R..._4core9panicking18panic_nounwind_fmt() falls through to next function _R..._4core9panicking5panic() The reason is that `rust_begin_unwind` is now mangled: _R..._7___rustc17rust_begin_unwind 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. Alternatively, we could remove the fixed one in `noreturn.h` and relax this test to cover both, but it seems best to be strict as long as we can. Cc: [email protected] # Needed in 6.12.y and later (Rust is pinned in older LTSs). Cc: Josh Poimboeuf <[email protected]> Cc: Peter Zijlstra <[email protected]> Reviewed-by: Alice Ryhl <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Miguel Ojeda <[email protected]>
Diffstat (limited to 'tools/testing/selftests/drivers/net/lib/py/remote_ssh.py')
0 files changed, 0 insertions, 0 deletions