From: Pnina Feder <pnina.feder@mobileye.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>, Mike Rapoport <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Cc: Dave Young <ruirui.yang@linux.dev>,
Jonathan Corbet <corbet@lwn.net>, Alexandre Ghiti <alex@ghiti.fr>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-doc@vger.kernel.org, Pnina Feder <pnina.feder@mobileye.com>
Subject: [PATCH 0/4] vmcore-tasks: export per-task metadata to vmcoreinfo
Date: Tue, 23 Jun 2026 00:14:26 +0300 [thread overview]
Message-ID: <20260622211430.4008899-1-pnina.feder@mobileye.com> (raw)
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/20260622205550.1087163-1-pnina.feder@mobileye.com/
The series is structured as follows:
Patch 1: Increase vmcoreinfo buffer from PAGE_SIZE to a fixed SZ_8K,
decoupled from page size to avoid waste on large-page
architectures (MIPS 16KB, arm64 64KB).
Patch 2: Export generic struct offsets (task_struct, mm_struct,
vm_area_struct, maple_tree, file/dentry/path, pt_regs,
signal_struct) needed to walk task lists and VMAs.
Patch 3: Export RISC-V arch-specific offsets (signal frame layouts,
register context structures) for user register extraction.
Patch 4: Export MIPS arch-specific offsets (signal frame layouts,
register context structures) for user register extraction.
Additional architecture support (arm64, x86, etc.) can follow the
same pattern established by patches 3 and 4.
Tested on MIPS64 (QEMU Malta) and RISC-V with full kdump pipeline:
primary kernel -> kexec panic -> crash kernel -> vmcore-tasks analysis.
Pnina Feder (4):
vmcoreinfo: increase vmcoreinfo buffer to 8KB
vmcoreinfo: export task and mm struct offsets to vmcoreinfo
riscv: vmcore_info: export riscv arch-specific struct offsets to
vmcoreinfo
mips: vmcore_info: export mips arch-specific struct offsets to
vmcoreinfo
.../admin-guide/kdump/vmcoreinfo.rst | 137 ++++++++++++++++++
arch/mips/kernel/Makefile | 1 +
arch/mips/kernel/signal.c | 8 +
arch/mips/kernel/vmcore_info.c | 22 +++
arch/riscv/kernel/signal.c | 8 +
arch/riscv/kernel/vmcore_info.c | 11 ++
include/linux/vmcore_info.h | 3 +-
kernel/vmcore_info.c | 60 ++++++++
8 files changed, 249 insertions(+), 1 deletion(-)
create mode 100644 arch/mips/kernel/vmcore_info.c
--
2.43.0
next reply other threads:[~2026-06-22 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 21:14 Pnina Feder [this message]
2026-06-22 21:14 ` [PATCH 1/4] vmcoreinfo: increase vmcoreinfo buffer to 8KB Pnina Feder
2026-06-22 21:14 ` [PATCH 2/4] vmcoreinfo: export task and mm struct offsets to vmcoreinfo Pnina Feder
2026-06-22 21:14 ` [PATCH 3/4] riscv: vmcore_info: export riscv arch-specific " Pnina Feder
2026-06-22 21:14 ` [PATCH 4/4] mips: vmcore_info: export mips " Pnina Feder
2026-07-07 6:21 ` [PATCH 0/4] vmcore-tasks: export per-task metadata " Mike Rapoport
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260622211430.4008899-1-pnina.feder@mobileye.com \
--to=pnina.feder@mobileye.com \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=bhe@redhat.com \
--cc=corbet@lwn.net \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pasha.tatashin@soleen.com \
--cc=pjw@kernel.org \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=ruirui.yang@linux.dev \
--cc=tsbogend@alpha.franken.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox