From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: <will@kernel.org>, <akpm@linux-foundation.org>,
<baoquan.he@linux.dev>, <rppt@kernel.org>,
<pasha.tatashin@soleen.com>, <pratyush@kernel.org>,
<thuth@redhat.com>, <mark.rutland@arm.com>, <jic23@kernel.org>,
<james.morse@arm.com>, <ardb@kernel.org>, <leitao@debian.org>,
<yeoreum.yun@arm.com>, <sourabhjain@linux.ibm.com>,
<robh@kernel.org>, <kees@kernel.org>, <coxu@redhat.com>,
<makb@juniper.net>, <piliu@redhat.com>, <graf@amazon.com>,
<ebiggers@kernel.org>, <jbouron@amazon.com>, <bgwin@google.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <kexec@lists.infradead.org>
Subject: Re: [PATCH v2 0/5] arm64: crash: Add crash hotplug support
Date: Fri, 14 Aug 2026 09:15:58 +0800 [thread overview]
Message-ID: <64f3a67a-51c6-4c01-a23b-301b619f2884@huawei.com> (raw)
In-Reply-To: <an3Xe_5-B4qdiN8o@arm.com>
在 2026/8/13 22:40, Catalin Marinas 写道:
> On Wed, Jul 29, 2026 at 11:12:30AM +0800, Jinjie Ruan wrote:
>> When CPU or memory hotplug events occur, the elfcorehdr in the kdump
>> image becomes stale, potentially leading to incomplete crash dumps.
>>
>> Currently, userspace udev rules reload the entire kdump image upon such
>> events, which is inefficient and leaves kdump inactive for a long time.
>>
>> Commit 247262756121 ("crash: add generic infrastructure for crash hotplug
>> support") introduced a kernel mechanism to update only the elfcorehdr.
>> This patch set implements crash hotplug support for arm64.
>>
>> As Baoquan suggested, it also addresses and fixes several
>> pre-existing code issues and Sashiko AI review findings extracted
>> from the previous patch set.
>>
>> The major improvements and fixes included in this series are:
>> - Fix several memory leaks for arm64.
>> - Simplify arm64 load_other_segments().
>> - Implement infrastructure for arm64 crash memory hotplug support.
>>
>> This patch set is rebased on liveupdate/crashkernel-cma.
>>
>> Link: https://lore.kernel.org/all/20260601094805.2928614-1-ruanjinjie@huawei.com/
>
> Is there any dependency for the first 3 patches on the above branch?
Hi Catalin,
The first three patches have no dependencies, only the last two patches
have dependencies
> Patches 2/3 look like fixes and they depend on patch 1. Not sure about
> cc stable, maybe patch 2.
Yes, you are right! The cc stable label has been added to patch 2 and
patch 3, I think both of them are needed.
>
> [...]
>
>> Jinjie Ruan (5):
>> kexec: Extract kexec_free_segment_cma() from kimage_free_cma()
>> arm64: kexec_file: Fix CMA page leaks in segment placement retry loops
>> arm64: kexec_file: Fix image->elf_headers memory leak in retry loop
>> arm64: kexec_file: Simplify load_other_segments()
>> arm64: crash: Add crash hotplug support
>
prev parent reply other threads:[~2026-08-14 1:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 3:12 [PATCH v2 0/5] arm64: crash: Add crash hotplug support Jinjie Ruan
2026-07-29 3:12 ` [PATCH v2 1/5] kexec: Extract kexec_free_segment_cma() from kimage_free_cma() Jinjie Ruan
2026-07-29 3:12 ` [PATCH v2 2/5] arm64: kexec_file: Fix CMA page leaks in segment placement retry loops Jinjie Ruan
2026-07-29 3:12 ` [PATCH v2 3/5] arm64: kexec_file: Fix image->elf_headers memory leak in retry loop Jinjie Ruan
2026-07-29 3:12 ` [PATCH v2 4/5] arm64: kexec_file: Simplify load_other_segments() Jinjie Ruan
2026-07-29 3:12 ` [PATCH v2 5/5] arm64: crash: Add crash hotplug support Jinjie Ruan
2026-08-13 16:05 ` Catalin Marinas
2026-08-17 10:45 ` Jinjie Ruan
2026-08-11 13:05 ` [PATCH v2 0/5] " Jinjie Ruan
2026-08-13 14:40 ` Catalin Marinas
2026-08-14 1:15 ` Jinjie Ruan [this message]
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=64f3a67a-51c6-4c01-a23b-301b619f2884@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=baoquan.he@linux.dev \
--cc=bgwin@google.com \
--cc=catalin.marinas@arm.com \
--cc=coxu@redhat.com \
--cc=ebiggers@kernel.org \
--cc=graf@amazon.com \
--cc=james.morse@arm.com \
--cc=jbouron@amazon.com \
--cc=jic23@kernel.org \
--cc=kees@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=leitao@debian.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=makb@juniper.net \
--cc=mark.rutland@arm.com \
--cc=pasha.tatashin@soleen.com \
--cc=piliu@redhat.com \
--cc=pratyush@kernel.org \
--cc=robh@kernel.org \
--cc=rppt@kernel.org \
--cc=sourabhjain@linux.ibm.com \
--cc=thuth@redhat.com \
--cc=will@kernel.org \
--cc=yeoreum.yun@arm.com \
/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