[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251216132801.807260-1-pnina.feder@mobileye.com>
Date: Tue, 16 Dec 2025 15:27:59 +0200
From: Pnina Feder <pnina.feder@...ileye.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
Baoquan He <bhe@...hat.com>
Cc: Vivek Goyal <vgoyal@...hat.com>,
Dave Young <dyoung@...hat.com>,
kexec@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Pnina Feder <pnina.feder@...ileye.com>
Subject: [PATCH 0/2] vmcoreinfo: support VMCOREINFO_BYTES larger than PAGE_SIZE
VMCOREINFO_BYTES is defined as a configurable size, but multiple
code paths implicitly assume it always fits into a single page.
This series removes that assumption by allocating and mapping
vmcoreinfo based on its actual size.
Patch 1 updates vmcoreinfo allocation to use get_order(VMCOREINFO_BYTES).
Patch 2 updates crash kernel handling to correctly allocate and map
multiple pages when copying vmcoreinfo.
This makes vmcoreinfo size consistent across the kernel and avoids
future breakage if VMCOREINFO_BYTES grows.
Tested on riscv64.
(No functional change when VMCOREINFO_BYTES == PAGE_SIZE.)
Pnina Feder (2):
kernel: vmcoreinfo: allocate vmcoreinfo_data based on VMCOREINFO_BYTES
kernel/crash: handle multi-page vmcoreinfo in crash kernel copy
kernel/crash_core.c | 17 +++++++++++++----
kernel/vmcore_info.c | 6 ++++--
2 files changed, 17 insertions(+), 6 deletions(-)
--
2.43.0
Powered by blists - more mailing lists