Re: [PATCH 0/3] kexec: Fix invalid field access - patchwork-bot+linux-riscv

From: patchwork-bot+linux-riscv@kernel.org
To: Breno Leitao <leitao@debian.org>
Cc: linux-riscv@lists.infradead.org, catalin.marinas@arm.com,
	will@kernel.org, akpm@linux-foundation.org, bhe@redhat.com,
	coxu@redhat.com, paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, alex@ghiti.fr, hca@linux.ibm.com,
	gor@linux.ibm.com, agordeev@linux.ibm.com,
	borntraeger@linux.ibm.com, svens@linux.ibm.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	kernel-team@meta.com
Subject: Re: [PATCH 0/3] kexec: Fix invalid field access
Date: Wed, 17 Sep 2025 02:40:16 +0000	[thread overview]
Message-ID: <175807681600.1444719.17902386827099362069.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250827-kbuf_all-v1-0-1df9882bb01a@debian.org>

Hello:

This series was applied to riscv/linux.git (for-next)
by Paul Walmsley <pjw@kernel.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

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv