[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<175807681600.1444719.17902386827099362069.git-patchwork-notify@kernel.org>
Date: Wed, 17 Sep 2025 02:40:16 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Breno Leitao <leitao@...ian.org>
Cc: linux-riscv@...ts.infradead.org, catalin.marinas@....com, will@...nel.org,
akpm@...ux-foundation.org, bhe@...hat.com, coxu@...hat.com,
paul.walmsley@...ive.com, palmer@...belt.com, aou@...s.berkeley.edu,
alex@...ti.fr, hca@...ux.ibm.com, gor@...ux.ibm.com, agordeev@...ux.ibm.com,
borntraeger@...ux.ibm.com, svens@...ux.ibm.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-s390@...r.kernel.org, kernel-team@...a.com
Subject: Re: [PATCH 0/3] kexec: Fix invalid field access
Hello:
This series was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@...nel.org>:
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
Powered by blists - more mailing lists