From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Sourabh Jain <sourabhjain@linux.ibm.com>, <corbet@lwn.net>,
<catalin.marinas@arm.com>, <will@kernel.org>,
<chenhuacai@kernel.org>, <kernel@xen0n.name>,
<maddy@linux.ibm.com>, <mpe@ellerman.id.au>, <npiggin@gmail.com>,
<chleroy@kernel.org>, <pjw@kernel.org>, <palmer@dabbelt.com>,
<aou@eecs.berkeley.edu>, <alex@ghiti.fr>, <tglx@kernel.org>,
<mingo@redhat.com>, <bp@alien8.de>, <dave.hansen@linux.intel.com>,
<hpa@zytor.com>, <akpm@linux-foundation.org>, <bhe@redhat.com>,
<vgoyal@redhat.com>, <dyoung@redhat.com>, <rdunlap@infradead.org>,
<pmladek@suse.com>, <feng.tang@linux.alibaba.com>,
<pawan.kumar.gupta@linux.intel.com>, <kees@kernel.org>,
<elver@google.com>, <arnd@arndb.de>, <lirongqing@baidu.com>,
<fvdl@google.com>, <leitao@debian.org>, <rppt@kernel.org>,
<ardb@kernel.org>, <jbohac@suse.cz>, <osandov@fb.com>,
<ryan.roberts@arm.com>, <cfsworks@gmail.com>,
<tangyouling@kylinos.cn>, <ritesh.list@gmail.com>,
<thuth@redhat.com>, <hbathini@linux.ibm.com>,
<eajames@linux.ibm.com>, <bjorn@rivosinc.com>,
<songshuaishuai@tinylab.org>, <kevin.brodsky@arm.com>,
<samuel.holland@sifive.com>, <vishal.moola@gmail.com>,
<junhui.liu@pigmoral.tech>, <dwmw@amazon.co.uk>,
<pbonzini@redhat.com>, <thomas.lendacky@amd.com>,
<kai.huang@intel.com>, <ubizjak@gmail.com>, <coxu@redhat.com>,
<liaoyuanhong@vivo.com>, <fuqiang.wang@easystack.cn>,
<brgerst@gmail.com>, <x86@kernel.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<loongarch@lists.linux.dev>, <linuxppc-dev@lists.ozlabs.org>,
<linux-riscv@lists.infradead.org>, <kexec@lists.infradead.org>
Subject: Re: [PATCH v4 1/3] crash: Exclude crash kernel memory in crash core
Date: Thu, 12 Feb 2026 11:28:42 +0800 [thread overview]
Message-ID: <31c2ae53-cbb7-bfad-9b8f-f9e1a254491e@huawei.com> (raw)
In-Reply-To: <50693f0c-c610-4347-86aa-40d50dc681fc@linux.ibm.com>
On 2026/2/10 20:30, Sourabh Jain wrote:
> Hello Jinjie,
>
> On 09/02/26 15:29, Jinjie Ruan wrote:
>> The exclude of crashk_res, crashk_low_res and crashk_cma memory
>> are almost identical across different architectures, handling them
>> in the crash core would eliminate a lot of duplication, so do
>> them in the common code.
>>
>> And move the size calculation (and the realloc if needed) into the
>> generic crash core so that:
>>
>> - New CMA regions or future crash-memory types can automatically
>> accounted for in crash core;
>>
>> - Each architecture no longer has to play whack-a-mole with
>> its private array size.
>>
>> To achieve the above goal, 4 architecture-specific functions are
>> introduced:
>>
>> - arch_get_system_nr_ranges() and arch_prepare_elf64_ram_headers().
>> The 1st function pre-counts the number of memory ranges, and
>> the 2st function fill the memory ranges into the cmem->ranges[] array,
>> and count the actual number of ranges filled. The default
>> implementation
>> is consistent with arm64 and loongson.
>>
>> - arch_crash_exclude_mem_range(). Realloc for powerpc. The default
>> implementation is crash_exclude_mem_range(), and use
>> crash_exclude_mem_range_guarded() to implement the arch version
>> for powerpc.
>>
>> - arch_get_crash_memory_ranges(). Get crash memory ranges for arch and
>> the default implementation is generic across x86, arm64, riscv, and
>> loongson by using the first two arch functions above. powerpc has its
>> own implementation by calling get_crash_memory_ranges().
>>
>> Tested on x86, arm64 and riscv with QEMU.
>>
>> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
>> ---
>> arch/arm64/kernel/machine_kexec_file.c | 47 +--------
>> arch/loongarch/kernel/machine_kexec_file.c | 45 +-------
>> arch/powerpc/include/asm/kexec.h | 13 +++
>> arch/powerpc/kexec/crash.c | 52 ++++++----
>> arch/powerpc/kexec/file_load_64.c | 17 ++-
>> arch/powerpc/kexec/ranges.c | 18 +---
>> arch/riscv/include/asm/kexec.h | 10 ++
>> arch/riscv/kernel/machine_kexec_file.c | 37 ++-----
>> arch/x86/include/asm/kexec.h | 10 ++
>> arch/x86/kernel/crash.c | 104 ++-----------------
>> include/linux/crash_core.h | 114 +++++++++++++++++++--
>> kernel/crash_core.c | 71 +++++++++++--
>> 12 files changed, 269 insertions(+), 269 deletions(-)
>>
[...]
>> extern void crash_ipi_callback(struct pt_regs *regs);
>> diff --git a/arch/powerpc/kexec/crash.c b/arch/powerpc/kexec/crash.c
>> index a325c1c02f96..5ade9a853fb0 100644
>> --- a/arch/powerpc/kexec/crash.c
>> +++ b/arch/powerpc/kexec/crash.c
>> @@ -419,30 +419,21 @@ unsigned int arch_crash_get_elfcorehdr_size(void)
>> return sizeof(struct elfhdr) + (phdr_cnt * sizeof(Elf64_Phdr));
>> }
>> -/**
>> - * update_crash_elfcorehdr() - Recreate the elfcorehdr and replace it
>> with old
>> - * elfcorehdr in the kexec segment array.
>> - * @image: the active struct kimage
>> - * @mn: struct memory_notify data handler
>> - */
>> -static void update_crash_elfcorehdr(struct kimage *image, struct
>> memory_notify *mn)
>> +int arch_get_crash_memory_ranges(struct crash_mem **cmem, unsigned
>> long *nr_mem_ranges,
>> + struct kimage *image, struct memory_notify *mn)
>> {
>> + unsigned long base_addr, size;
>> int ret;
>> - struct crash_mem *cmem = NULL;
>> - struct kexec_segment *ksegment;
>> - void *ptr, *mem, *elfbuf = NULL;
>> - unsigned long elfsz, memsz, base_addr, size;
>> - ksegment = &image->segment[image->elfcorehdr_index];
>> - mem = (void *) ksegment->mem;
>> - memsz = ksegment->memsz;
>> -
>> - ret = get_crash_memory_ranges(&cmem);
>> + ret = get_crash_memory_ranges(cmem);
>> if (ret) {
>> pr_err("Failed to get crash mem range\n");
>> - return;
>> + return ret;
>> }
>> + if (!image || !mn)
>> + return 0;
>> +
>> /*
>> * The hot unplugged memory is part of crash memory ranges,
>> * remove it here.
>> @@ -450,14 +441,34 @@ static void update_crash_elfcorehdr(struct
>> kimage *image, struct memory_notify *
>> if (image->hp_action == KEXEC_CRASH_HP_REMOVE_MEMORY) {
>> base_addr = PFN_PHYS(mn->start_pfn);
>> size = mn->nr_pages * PAGE_SIZE;
>> - ret = remove_mem_range(&cmem, base_addr, size);
>> + ret = remove_mem_range(cmem, base_addr, size);
>
> I like the overall design for handling crashkernel memory exclusion
> in this patch series, especially the way you managed to free the
> crash_mem object (mem) in the generic code (crash_prepare_elf64_headers()).
Thanks for the review.
>
> However, the way crash memory is prepared after a memory hotplug
> event on powerpc by calling remove_mem_range(), can leave the crash
> memory ranges unsorted. This can cause issues in the generic code
> when excluding crashkernel memory, because crash_exclude_mem_range()
> expects crash_mem to be sorted.
You are absolutely correct.
>
> So I wrote a simple patch to cover this scenario. Including the
> patch below as the first patch in this series would be helpful.
> https://lore.kernel.org/all/20260210120803.433978-1-sourabhjain@linux.ibm.com/
Thanks for the additional patch. I'll add it as the first patch in the
next revision to ensure crash_mem remains sorted after memory hotplug
events on powerpc.
Best regards,
Jinjie
>
> Jinjie, will it be possible for you to include the above patch in this
> patch series?
My pleasure.
>> if (ret) {
>> pr_err("Failed to remove hot-unplugged memory from crash
>> memory ranges\n");
>> - goto out;
>> + return ret;
>> }
>> }
>> - ret = crash_prepare_elf64_headers(cmem, false, &elfbuf, &elfsz);
>> + return 0;
>> +}
>> +
>> +/**
>> + * update_crash_elfcorehdr() - Recreate the elfcorehdr and replace it
>> with old
>> + * elfcorehdr in the kexec segment array.
>> + * @image: the active struct kimage
>> + * @mn: struct memory_notify data handler
>> + */
>> +static void update_crash_elfcorehdr(struct kimage *image, struct
>> memory_notify *mn)
>> +{
>> + void *ptr, *mem, *elfbuf = NULL;
>> + struct kexec_segment *ksegment;
>> + unsigned long elfsz, memsz;
>> + int ret;
>> +
>> + ksegment = &image->segment[image->elfcorehdr_index];
>> + mem = (void *) ksegment->mem;
>> + memsz = ksegment->memsz;
>> +
>> + ret = crash_prepare_elf64_headers(false, &elfbuf, &elfsz, NULL,
>> image, mn);
>> if (ret) {
>> pr_err("Failed to prepare elf header\n");
>> goto out;
>> @@ -486,7 +497,6 @@ static void update_crash_elfcorehdr(struct kimage
>> *image, struct memory_notify *
>> xchg(&kexec_crash_image, image);
>> }
>> out:
>> - kvfree(cmem);
>> kvfree(elfbuf);
>> }
[...]
>> +int crash_prepare_elf64_headers(int need_kernel_map, void **addr,
>> + unsigned long *sz, unsigned long *nr_mem_ranges,
>> + struct kimage *image, struct memory_notify *mn)
>> {
>> - Elf64_Ehdr *ehdr;
>> - Elf64_Phdr *phdr;
>> unsigned long nr_cpus = num_possible_cpus(), nr_phdr, elf_sz;
>> - unsigned char *buf;
>> - unsigned int cpu, i;
>> unsigned long long notes_addr;
>> + struct crash_mem *mem = NULL;
>> unsigned long mstart, mend;
>> + unsigned int cpu, i;
>> + unsigned char *buf;
>> + Elf64_Ehdr *ehdr;
>> + Elf64_Phdr *phdr;
>> + int ret = 0;
>> +
>> + ret = arch_get_crash_memory_ranges(&mem, nr_mem_ranges, image, mn);
>> + if (ret)
>> + return ret;
>> +
>> + if (mem) {
>> + ret = crash_exclude_mem_ranges(mem, nr_mem_ranges);
>> + if (ret)
>> + goto out;
>> + }
>> /* extra phdr for vmcoreinfo ELF note */
>> nr_phdr = nr_cpus + 1;
>> @@ -192,8 +240,10 @@ int crash_prepare_elf64_headers(struct crash_mem
>> *mem, int need_kernel_map,
>> elf_sz = ALIGN(elf_sz, ELF_CORE_HEADER_ALIGN);
>> buf = vzalloc(elf_sz);
>> - if (!buf)
>> - return -ENOMEM;
>> + if (!buf) {
>> + ret = -ENOMEM;
>> + goto out;
>> + }
>> ehdr = (Elf64_Ehdr *)buf;
>> phdr = (Elf64_Phdr *)(ehdr + 1);
>> @@ -262,7 +312,10 @@ int crash_prepare_elf64_headers(struct crash_mem
>> *mem, int need_kernel_map,
>> *addr = buf;
>> *sz = elf_sz;
>> - return 0;
>> +
>> +out:
>> + kvfree(mem);
>> + return ret;
>> }
>> /**
>
next prev parent reply other threads:[~2026-02-12 3:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 9:59 [PATCH v4 0/3] arm64/riscv: Add support for crashkernel CMA reservation Jinjie Ruan
2026-02-09 9:59 ` [PATCH v4 1/3] crash: Exclude crash kernel memory in crash core Jinjie Ruan
2026-02-10 12:30 ` Sourabh Jain
2026-02-12 3:28 ` Jinjie Ruan [this message]
2026-02-12 6:11 ` Sourabh Jain
2026-02-09 9:59 ` [PATCH v4 2/3] arm64: kexec: Add support for crashkernel CMA reservation Jinjie Ruan
2026-02-09 9:59 ` [PATCH v4 3/3] riscv: " Jinjie Ruan
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=31c2ae53-cbb7-bfad-9b8f-f9e1a254491e@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--cc=bjorn@rivosinc.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=cfsworks@gmail.com \
--cc=chenhuacai@kernel.org \
--cc=chleroy@kernel.org \
--cc=corbet@lwn.net \
--cc=coxu@redhat.com \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw@amazon.co.uk \
--cc=dyoung@redhat.com \
--cc=eajames@linux.ibm.com \
--cc=elver@google.com \
--cc=feng.tang@linux.alibaba.com \
--cc=fuqiang.wang@easystack.cn \
--cc=fvdl@google.com \
--cc=hbathini@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=jbohac@suse.cz \
--cc=junhui.liu@pigmoral.tech \
--cc=kai.huang@intel.com \
--cc=kees@kernel.org \
--cc=kernel@xen0n.name \
--cc=kevin.brodsky@arm.com \
--cc=kexec@lists.infradead.org \
--cc=leitao@debian.org \
--cc=liaoyuanhong@vivo.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lirongqing@baidu.com \
--cc=loongarch@lists.linux.dev \
--cc=maddy@linux.ibm.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=osandov@fb.com \
--cc=palmer@dabbelt.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=pjw@kernel.org \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=ritesh.list@gmail.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=samuel.holland@sifive.com \
--cc=songshuaishuai@tinylab.org \
--cc=sourabhjain@linux.ibm.com \
--cc=tangyouling@kylinos.cn \
--cc=tglx@kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=thuth@redhat.com \
--cc=ubizjak@gmail.com \
--cc=vgoyal@redhat.com \
--cc=vishal.moola@gmail.com \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/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