Thread (9 messages) read the whole thread 9 messages, 4 authors, 2025-09-17

Re: [PATCH 0/3] kexec: Fix invalid field access

From: patchwork-bot+linux-riscv@kernel.org
Date: 2025-09-17 02:40:15
Also in: linux-riscv, linux-s390, lkml

Hello:

This series was applied to riscv/linux.git (for-next)
by Paul Walmsley [off-list ref]:

On Wed, 27 Aug 2025 03:42:20 -0700 you wrote:
The kexec_buf structure was previously declared without initialization.
commit bf454ec31add ("kexec_file: allow to place kexec_buf randomly")
added a field that is always read but not consistently populated by all
architectures. This un-initialized field will contain garbage.

This is also triggering a UBSAN warning when the uninitialized data was
accessed:

[...]
Here is the summary with links:
  - [1/3] arm64: kexec: Initialize kexec_buf struct in load_other_segments()
    (no matching commit)
  - [2/3] riscv: kexec: Initialize kexec_buf struct
    https://git.kernel.org/riscv/c/95c54cd9c769
  - [3/3] s390: kexec: Initialize kexec_buf struct
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html


Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help