linux-stable.git/Makefile, branch v7.2.4

Linux 7.2.4

2026-09-07T15:37:28+00:00

Link: https://lore.kernel.org/r/20260904045803.810145556@linuxfoundation.org
Tested-by: Takeshi Ogasawara 
Tested-by: Ronald Warsow 
Tested-by: Brett A C Sheffield 
Tested-by: Markus Reichelt 
Tested-by: Shuah Khan 
Tested-by: Salvatore Bonaccorso 
Tested-by: Miguel Ojeda 
Tested-by: Barry K. Nathan 
Tested-by: Peter Schneider 
Tested-by: Ron Economos 
Tested-by: Benjamin Boortz 
Tested-by: Jeffrin Jose T 
Signed-off-by: Greg Kroah-Hartman

kbuild: rust: preserve unreachable traps with inline helpers

2026-09-07T15:36:32+00:00

commit 0bff7711c19ba05ff3b686554c5a2d503c3e9797 upstream.

When `CONFIG_RUST_INLINE_HELPERS` is enabled, it is possible to hit
`objtool` warnings like:

    vmlinux.o: warning: objtool: _R..._4cmdq12CommandToGsp4init()
    falls through to next function _R..._4core5array4iter8IntoIterRShKj3_EEEBa_()

`rustc` normally emits traps for unreachable paths. However, under
`CONFIG_RUST_INLINE_HELPERS=y`, `rustc` emits LLVM bitcode and Clang
performs final code generation after the helper bitcode is linked,
but Clang does not trap unreachable IR by default.

In turn, this means `objtool` follows compiler-generated impossible Rust
`enum` paths through alignment padding into the next function, resulting
in fallthrough warnings.

Thus pass the LLVM `trap-unreachable` option to the final Clang invocation
and suppress traps immediately after `noreturn` calls, which `objtool`
already recognizes as dead ends. The combination of both flags makes it
match `rustc`'s behavior.

Rust 1.85.0 (the minimum supported one) supports LLVM >= 18, and both
flags are available in LLVM 18.

Assisted-by: LLM
Cc: Gary Guo 
Cc: Boqun Feng 
Cc: Alice Ryhl 
Cc: Matthew Maurer 
Cc: Josh Poimboeuf 
Cc: Peter Zijlstra 
Cc: stable@vger.kernel.org
Fixes: 3a2486cc1da5 ("kbuild: rust: provide an option to inline C helpers into Rust")
Acked-by: Gary Guo 
Link: https://patch.msgid.link/20260816133233.197500-1-ojeda@kernel.org
Signed-off-by: Miguel Ojeda 
Signed-off-by: Greg Kroah-Hartman

rust: cfi: disable function merging if CFI is enabled

2026-09-07T15:36:32+00:00

commit 29b03d1de967a177176d12811d970cac7882afcf upstream.

In Rust doc tests, there is a dummy `__module_firmware_test_init` function
generated by the example in `module_firmware!`'s documentation, which
just returns zero. Many other documentation examples generate functions
that produce zero. LKP test robot reports [1] a `Flags::zeroed` instance;
my local reproduction has a `Bounded::new::<0>`.

LLVM's MergeFunctionsPass incorrectly merges functions with different
KCFI types, causing `__module_firmware_test_init` to be merged into
one of the zero-returning functions. As module init is invoked via an
indirect function call, KCFI is checked and this produces a KCFI failure.

I've reported this bug to upstream LLVM [2]; in the meantime, disable
function merging if CFI is enabled. No separate treatment is needed for
CONFIG_RUST_INLINE_HELPERS, as Clang does not enable function merging
by default.

[ LLVM already has a pending PR:

    https://github.com/llvm/llvm-project/pull/217665

  which solves the issue. In addition, I asked upstream Rust if the
  unstable `-Zmerge-functions=disabled` flag will remain around:

    https://rust-lang.zulipchat.com/#narrow/channel/425075-rust-for-linux/topic/.60-Zmerge-functions.3Ddisabled.60/

  and it does indeed look like that will be the case. - Miguel ]

Reported-by: kernel test robot 
Closes: https://lore.kernel.org/oe-lkp/202608201017.100a4511-lkp@intel.com [1]
Link: https://github.com/llvm/llvm-project/issues/217629 [2]
Signed-off-by: Gary Guo 
Cc: stable@vger.kernel.org
Fixes: ca627e636551 ("rust: cfi: add support for CFI_CLANG with Rust")
Reviewed-by: Sami Tolvanen 
Link: https://patch.msgid.link/20260820135733.37121-1-gary@kernel.org
[ Fixed typos as discussed. Reworded slightly for other typos. - Miguel ]
Signed-off-by: Miguel Ojeda 
Signed-off-by: Greg Kroah-Hartman

Linux 7.2.3

2026-09-02T12:33:21+00:00

Link: https://lore.kernel.org/r/20260831133359.055927882@linuxfoundation.org
Tested-by: Ronald Warsow 
Tested-by: Brett A C Sheffield 
Tested-by: Florian Fainelli 
Tested-by: Salvatore Bonaccorso 
Tested-by: Peter Schneider 
Tested-by: Takeshi Ogasawara 
Tested-by: Shuah Khan 
Tested-by: Miguel Ojeda 
Tested-by: Ron Economos 
Tested-by: Barry K. Nathan 
Signed-off-by: Greg Kroah-Hartman

Linux 7.2.2

2026-08-28T06:25:22+00:00

Signed-off-by: Greg Kroah-Hartman

Linux 7.2.1

2026-08-27T12:35:27+00:00

Link: https://lore.kernel.org/r/20260825132541.560541185@linuxfoundation.org
Tested-by: Ronald Warsow 
Tested-by: Justin M. Forbes 
Tested-by: Florian Fainelli 
Tested-by: Shuah Khan 
Tested-by: Ron Economos 
Tested-by: Barry K. Nathan 
Tested-by: Salvatore Bonaccorso 
Tested-by: Brett A C Sheffield 
Tested-by: Miguel Ojeda 
Tested-by: Krzysztof Wilczyński 
Tested-by: Peter Schneider 
Tested-by: Benjamin Boortz 
Tested-by: Mark Brown 
Signed-off-by: Greg Kroah-Hartman

Linux 7.2

2026-08-16T21:32:26+00:00

Linux 7.2-rc7

2026-08-09T21:54:50+00:00

Linux 7.2-rc6

2026-08-02T23:24:24+00:00

Merge tag 'kbuild-fixes-7.2-1' of git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux

2026-08-01T03:45:28+00:00

Pull Kbuild fixes from Nathan Chancellor:

 - Fix regression with MO= when building out of tree kernel modules due
   to incorrectly overwriting build tree's Makefile

 - Avoid stripping .BTF sections from modules when building debug .rpm
   packages

* tag 'kbuild-fixes-7.2-1' of git://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux:
  kbuild: rpm-pkg: Preserve BTF sections in kernel modules during debuginfo stripping
  kbuild: Stop modifying $(objtree)/Makefile when building oot-kmods oos