From: Miguel Ojeda <ojeda@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "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>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Tamir Duberstein" <tamird@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Onur Özkan" <work@onurozkan.dev>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Rust fixes for 7.4 (4th)
Date: Sun, 22 Nov 2026 13:25:25 +0100 [thread overview]
Message-ID: <20261122122525.71959-1-ojeda@kernel.org> (raw)
Hi Linus,
Please pull these fixes for Rust.
They have been in linux-next for two rounds or more.
No conflicts expected.
Thanks!
Cheers,
Miguel
The following changes since commit aebb7274476403040d582c61478df8f4a7bf9cd3:
Linux 7.4-rc3 (2026-11-15 14:30:11 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/ojeda/linux.git tags/rust-fixes-7.4-4
for you to fetch changes up to 73bdf8773de4af2c2b7f49370191ae6d5aeddea5:
kbuild: rust: disable function merging unconditionally (2026-11-19 11:28:42 +0100)
----------------------------------------------------------------
Rust fixes for v7.4 (4th)
Toolchain and infrastructure:
- Disable function merging in all cases to fix broken MODVERSIONS
information with gendwarfksyms, wrong backtraces and possibly issues
with pahole/BTF due to lost debug information.
- x86: emit the expected 'cs' prefix for RETPOLINE builds by passing
the '-Zindirect-branch-cs-prefix' flag we added to 'rustc', which
fixes boot failures (with 'spectre_v2=retpoline,lfence') and code
corruption (with paranoid FineIBT).
- Fix objtool warnings for the upcoming Rust 1.101.0 (expected
2026-12-24) by adding more 'noreturn' functions.
'kernel' crate:
- 'str' module: fix soundness issue in 'Formatter::new()' by tying the
returned formatter to the lifetime of its backing buffer.
- 'iov' module: fix soundness issue in 'copy_from_iter_raw()' by tying
the returned slice to the lifetime of the output buffer.
I suggested upstream Rust to introduce a lint for this case of the
lifetime elision rule, to avoid repeating this sort of mistake.
----------------------------------------------------------------
Alice Ryhl (1):
kbuild: rust: disable function merging unconditionally
Marwan Mohamed Zein (1):
rust: iov: fix return lifetime of `copy_from_iter_raw()`
Miguel Ojeda (2):
objtool/rust: add more `noreturn` Rust functions for Rust 1.101.0
x86/rust: use `-Zindirect-branch-cs-prefix` for RETPOLINE builds
Peder Bergan (1):
rust: str: tie Formatter to its backing buffer
Makefile | 4 ++--
arch/x86/Makefile | 1 +
rust/Makefile | 2 +-
rust/kernel/iov.rs | 2 +-
rust/kernel/str.rs | 4 ++--
tools/objtool/check.c | 4 ++++
6 files changed, 11 insertions(+), 6 deletions(-)
reply other threads:[~2026-11-22 12:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261122122525.71959-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=torvalds@linux-foundation.org \
--cc=work@onurozkan.dev \
/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