Re: [PATCH 0/4] vmcore-tasks: export per-task metadata to vmcoreinfo

Mike Rapoport <[email protected]>
Newsgroups org.infradead.lists.kexec,org.infradead.lists.linux-riscv,org.kernel.vger.linux-doc,org.kernel.vger.linux-kernel,org.kernel.vger.linux-mips
Message-ID <[email protected]>
(adding new Baoquan's email)

Hi Pnina,
On Tue, Jun 23, 2026 at 12:14:26AM +0300, Pnina Feder wrote:
> This series extends vmcoreinfo with struct offsets and sizes needed by
> the vmcore-tasks userspace tool to extract per-task state from a vmcore
> dump without requiring kernel debug symbols (DWARF/BTF).
> 
> The vmcore-tasks tool reads /proc/vmcore (or a saved vmcore file) and
> reconstructs, for each task:
>   - task name, pid, state, flags
>   - VMA list (start, end, flags, backing file)
>   - user register state (saved on the kernel stack at kernel entry)
>   - user-space backtrace with VMA/filename mapping
>   - kernel dmesg buffer
> 
> This provides a lightweight post-mortem crash analysis capability for
> production environments where full debug info (DWARF/BTF) is not
> available.
> 
> The companion userspace tool is submitted to kexec-tools:
>   https://lore.kernel.org/all/[email protected]/

Sorry for the delay, this fell between the cracks somehow.

The kernel side looks fine overall, but to merge it there should be an agreement
from the userspace side maintainers that vmcore-tasks is something they are
wishing to accept.

-- 
Sincerely yours,
Mike.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.