diff options
| author | Miguel Ojeda <[email protected]> | 2025-01-12 14:39:51 +0000 |
|---|---|---|
| committer | Miguel Ojeda <[email protected]> | 2025-02-12 22:26:48 +0000 |
| commit | cee6f9a9c87b6ecfb51845950c28216b231c3610 (patch) | |
| tree | 8ab109d1fe4fe4498121d90b9cc24c804ef599e2 /net/unix/garbage.c | |
| parent | Linux 6.14-rc2 (diff) | |
| download | kernel-cee6f9a9c87b6ecfb51845950c28216b231c3610.tar.gz kernel-cee6f9a9c87b6ecfb51845950c28216b231c3610.zip | |
objtool/rust: add one more `noreturn` Rust function
Starting with Rust 1.85.0 (currently in beta, to be released 2025-02-20),
under some kernel configurations with `CONFIG_RUST_DEBUG_ASSERTIONS=y`,
one may trigger a new `objtool` warning:
rust/kernel.o: warning: objtool: _R...securityNtB2_11SecurityCtx8as_bytes()
falls through to next function _R...core3ops4drop4Drop4drop()
due to a call to the `noreturn` symbol:
core::panicking::assert_failed::<usize, usize>
Thus add it to the list so that `objtool` knows it is actually `noreturn`.
Do so matching with `strstr` since it is a generic.
See commit 56d680dd23c3 ("objtool/rust: list `noreturn` Rust functions")
for more details.
Cc: [email protected] # Needed in 6.12.y and 6.13.y only (Rust is pinned in older LTSs).
Fixes: 56d680dd23c3 ("objtool/rust: list `noreturn` Rust functions")
Reviewed-by: Gary Guo <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
[ Updated Cc: stable@ to include 6.13.y. - Miguel ]
Signed-off-by: Miguel Ojeda <[email protected]>
Diffstat (limited to 'net/unix/garbage.c')
0 files changed, 0 insertions, 0 deletions
