linux-kernel - Re: [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: <87jz4txsjx.fsf@all.your.base.are.belong.to.us>
Date: Mon, 30 Jun 2025 15:33:38 +0200
From: Björn Töpel <bjorn@...nel.org>
To: Pnina Feder <pnina.feder@...ileye.com>
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: Re: [PATCH 0/1] Fix for riscv vmcore issue

Pnina!

Pnina Feder <pnina.feder@...ileye.com> writes:

> 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.

Thanks for reporting this!

> 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.

How are you collecting the /proc/vmcore file? A full set of commands
would be helpful.

> 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.

Wdym with "IRQ pointers"? Also, what version (sha1) of crash are you
using?


Thanks!
Björn