mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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.3
Date: Sun, 30 Aug 2026 11:38:34 +0200	[thread overview]
Message-ID: <20260830093834.275112-1-ojeda@kernel.org> (raw)

Hi Linus,

Please pull these fixes for Rust.

They have been in linux-next for at least 3 rounds (most for a week).

No conflicts expected.

Thanks!

Cheers,
Miguel

The following changes since commit d24f5cdbeff8b6a063fca92d0a1f94122a799b59:

  Merge tag 'rust-7.3' of git://git.kernel.org/pub/scm/linux/kernel/git/ojeda/linux (2026-08-18 11:25:09 -0700)

are available in the Git repository at:

  ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/ojeda/linux.git tags/rust-fixes-7.3

for you to fetch changes up to 1b0bab4a873f1034c27573cfc613394cff7e0a5b:

  rust: kbuild: disambiguate `zerocopy_derive` for `rusttest` (2026-08-25 22:19:27 +0200)

----------------------------------------------------------------
Rust fixes for v7.3

Toolchain and infrastructure:

 - Fix KCFI failures, such as in Rust doctests, by disabling function
   merging when CFI is enabled. Gary reported the LLVM bug to upstream
   and it is now fixed in their mainline.

 - Fix 'objtool' fallthrough warnings under the experimental
   'CONFIG_RUST_INLINE_HELPERS' by passing (for the combined Rust and
   helpers code) the LLVM options needed to preserve the unreachable
   traps that 'rustc' normally emits.

   In addition, fix 'objtool' errors when LTO is enabled on top, by
   also filtering out the LTO flags (for the combined Rust and helpers
   code) so that the traps are kept in place.

 - Fix 'objtool' warnings by adding one more 'noreturn' function.

 - Fix 'make rusttest' target when the 'rustc-dev' component is
   installed and Rust >= 1.82.0, <= 1.87.0 is used.

'kernel' crate:

 - 'num' module: fix soundness issue in the 'Bounded' conversion from
   'bool' by restricting the conversions to unsigned 'Bounded'.

 - 'jump_label' module: fix future 'make rusttest' target failures when
   'ARCH=' is set to an arch different than the host's.

 - 'list' module: fix incorrect 'pop_back()' comment.

----------------------------------------------------------------
FUJITA Tomonori (1):
      rust: jump_label: skip arch-specific asm in `testlib` builds

Gary Guo (1):
      rust: cfi: disable function merging if CFI is enabled

Miguel Ojeda (4):
      objtool/rust: add one more `noreturn` Rust function
      kbuild: rust: preserve unreachable traps with inline helpers
      kbuild: rust: keep Rust objects out of Clang LTO with inline helpers
      rust: kbuild: disambiguate `zerocopy_derive` for `rusttest`

Nikolai Grlica (1):
      rust: kernel: list: fix incorrect pop_back example comment

Younes Akhouayri (1):
      rust: num: restrict bool conversion to unsigned Bounded

 Makefile                   | 13 ++++++++++++-
 rust/Makefile              |  6 ++++--
 rust/kernel/jump_label.rs  | 12 ++++++++++++
 rust/kernel/list.rs        |  2 +-
 rust/kernel/num/bounded.rs | 30 +++++++++++++++++++++---------
 scripts/Makefile.build     |  3 ++-
 tools/objtool/check.c      |  1 +
 7 files changed, 53 insertions(+), 14 deletions(-)

                 reply	other threads:[~2026-08-30  9:38 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=20260830093834.275112-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

all inboxes | Powered by JetHome®