linux-kernel - [PATCH 0/1] Fix for riscv vmcore issue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250630112309.97162-2-pnina.feder@mobileye.com>
Date: Mon, 30 Jun 2025 14:21:28 +0300
From: Pnina Feder <pnina.feder@...ileye.com>
To: bjorn@...nel.org
Cc: alex@...ti.fr,
	bjorn@...osinc.com,
	linux-kernel@...r.kernel.org,
	linux-riscv@...ts.infradead.org,
	mick@....forth.gr,
	palmer@...belt.com,
	paul.walmsley@...ive.com,
	Pnina Feder <pnina.feder@...ileye.com>
Subject: [PATCH 0/1] Fix for riscv vmcore issue

We are creating a vmcore using kexec on a Linux 6.15 RISC-V system and analyzing it with the crash tool on the host.
This workflow used to work on Linux 6.14 but is now broken in 6.15.

The issue is caused by a change in the kernel:
In Linux 6.15, certain memblock sections are now marked as Reserved in /proc/iomem.
The kexec tool excludes all Reserved regions when generating the vmcore, so these sections are missing from the dump.

However, the kernel still uses addresses in these regions—for example, for IRQ pointers.
Since the crash tool needs access to these memory areas to function correctly, their exclusion breaks the analysis.

Pnina Feder (1):
  riscv: Change memblock reserved name to be recognized on kexec

 arch/riscv/kernel/setup.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.43.0