mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Baoquan He <baoquan.he@linux.dev>
To: Mike Rapoport <rppt@kernel.org>
Cc: Wandun <chenwandun1@gmail.com>,
	catalin.marinas@arm.com, will@kernel.org, chenhuacai@kernel.org,
	pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
	tglx@kernel.org, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, x86@kernel.org, robh@kernel.org,
	saravanak@kernel.org, akpm@linux-foundation.org,
	pasha.tatashin@soleen.com, pratyush@kernel.org,
	m.szyprowski@samsung.com, mark.rutland@arm.com,
	kernel@xen0n.name, alex@ghiti.fr, hpa@zytor.com,
	ruirui.yang@linux.dev, robin.murphy@arm.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
	linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
	kexec@lists.infradead.org, linux-mm@kvack.org,
	iommu@lists.linux.dev
Subject: Re: [PATCH v6 00/10] kdump: reduce vmcore size and capture time
Date: Fri, 18 Sep 2026 15:31:00 +0800	[thread overview]
Message-ID: <aqzotDs4yDRxgcWS@fedora> (raw)
In-Reply-To: <aqziOmx1yhy0ozkX@kernel.org>

On 09/18/26 at 10:03am, Mike Rapoport wrote:
> Hi,
> 
> On Tue, Sep 15, 2026 at 09:01:07PM +0800, Wandun wrote:
> > On 9/2/26 15:31, Wandun Chen wrote:
> > > From: Wandun Chen <chenwandun@lixiang.com>
...snip... 
> > > ACPI systems already filter reserved memory out of the vmcore through
> > > their existing path; only DT-based systems currently fail to filter these
> > > regions, which is what this series addresses. The flag lives in memblock
> > > itself rather than in a DT-only structure, so the mechanism is generic and
                                                                     ~~~~~~~
> > > both ACPI and DT systems can benefit from it (suggested by Rob, thanks) [1].
> > > 
> > > Since the reserved memory regions are filtered out, the vmcore is
> > > smaller in size and faster to produce. 
> > > 
> > > The series is based on linux-next and is organized as follows:
> > > 
> > > Patches 1-4: Preparation and bugfixes: fix the missing HugeTLB
> > >              flagname, switch riscv crash_mem to memblock, fold the
> > >              duplicated per-arch memblock walks into the weak
> > >              defaults, and serialize crash header preparation against
> > >              memory hotplug.
> > > Patches 5-9: NODUMP infrastructure: switch crash_core to
> > >              for_each_mem_region(), introduce the MEMBLOCK_NODUMP
> > >              flag, add a dumpable flag to struct reserved_mem, and
> > >              mark /reserved-memory and /memreserve/ entries with
> > > 	     MEMBLOCK_NODUMP flag.
> > > Patch 10:    Exclude MEMBLOCK_NODUMP regions from the vmcore ELF
> > >              header.
> > 
> > Hi,
> > 
> > Gentle ping on the remaining patches of this series.
> > Patches 1, 7, 8 and 9 have been reviewed (thanks Mike and Marek);
> > Still looking for review on patches 2-6 and 10.
> 
> I'm waiting for reviews from Baoquan and Dave for crash core patches before
> applying this series.

I will go through the crash core patches, thanks for reminding.

>  
> > Would appreciate a look when you have a moment, happy to rework
> > anything based on feedback.
> > 
> > Best regards,
> > Wanun
> > 
> > > 
> > > In v5, Sashiko found some pre-existing issues related to reserved-memory,
> > > and has no dependency on this series, so these issues have been addressed
> > > in a separate series [2].
> > > 
> > > v5 --> v6:
> > > 1. Serialize crash header preparation against memory hotplug to avoid
> > >    out-of-bounds or use-after-free issues.
> > > 
> > > 2. MEMBLOCK_NODUMP marking is now done after memblock allows resizing,
> > >    avoiding a panic from too few regions before resize is permitted.
> > > 
> > > 3. Reordered the patches, put pre-existing bugfixes earlier in the series.
> > > 
> > > 
> > > v4 --> v5:
> > > 1. Rework the mechanism around a memblock-level MEMBLOCK_NODUMP flag
> > >    (suggested by Rob) instead of the v4 opt-in 'dumpable' flag on
> > >    DT-only struct reserved_mem.
> > > 2. Switch the riscv vmcore elf header preparation to use memblock
> > >    instead of the resource tree, aligning it with arm64 and loongarch,
> > >    so riscv also can exclude reserved memory from vmcore.
> > > 3. Deduplicate the vmcore elf header preparation: arm64, riscv and
> > >    loongarch open-coded the same logic, so fold it into shared
> > >     __weak defaults in crash_core.
> > > 4.  Drop the v4 patch that saved /memreserve/ entries into the
> > >     reserved_mem array; /memreserve/ is now marked MEMBLOCK_NODUMP
> > >     directly.
> > > 
> > > v3 --> v4:
> > > 1. Rebase this series on v7.2-rc1.
> > > 2. Add two cleanup patches (patch 02/03).
> > > 3. Simplify patch 03 to avoid checking whether initial_boot_params is
> > >    NULL multiple times, suggested by Rob.
> > > 
> > > v2 --> v3:
> > > 1. Fix out-of-bounds issue if device tree lacks /reserved-memory node.
> > > 2. Fix UAF issue when alloc_reserved_mem_array() fails.
> > > 3. Add some prepare patches.
> > > 
> > > v1 --> v2:
> > > 1. v1 added an opt-out DT property ('linux,no-dump'). Per Rob's
> > >    feedback [3], v2 drop that property and exclude reserve memory
> > >    by default.
> > > 2. Split some prepared patches from the original patches.
> > > 3. Address coding-style comments on patch 5 from Rob.
> > > 
> > > [1] https://lore.kernel.org/lkml/20260723234126.GA3253409-robh@kernel.org/
> > > [2] https://lore.kernel.org/lkml/20260818092420.2859026-1-chenwandun1@gmail.com/
> > > [3] https://lore.kernel.org/lkml/20260506144542.GA2072596-robh@kernel.org/
> > > 
> > > Meijing Zhao (1):
> > >   mm: memblock: add missing HugeTLB flag name
> > > 
> > > Wandun Chen (9):
> > >   riscv: build crash_mem ranges from memblock instead of resource tree
> > >   crash_core: fold duplicated memblock arch hooks into the weak default
> > >   crash_core: serialize crash header preparation against hotplug
> > >   crash_core: replace for_each_mem_range() with for_each_mem_region()
> > >   memblock: introduce MEMBLOCK_NODUMP flag
> > >   of: reserved_mem: add dumpable flag to opt-in vmcore
> > >   of: reserved_mem: mark /reserved-memory entries with MEMBLOCK_NODUMP
> > >   of: reserved_mem: mark /memreserve/ entries as MEMBLOCK_NODUMP
> > >   crash_core: skip MEMBLOCK_NODUMP regions when building vmcore ELF
> > >     header
> > > 
> > >  arch/arm64/kernel/machine_kexec_file.c     | 29 ------------
> > >  arch/loongarch/kernel/machine_kexec_file.c | 27 ------------
> > >  arch/riscv/Kconfig                         |  2 +-
> > >  arch/riscv/kernel/machine_kexec_file.c     | 33 --------------
> > >  arch/x86/kernel/crash.c                    |  2 +-
> > >  drivers/of/fdt.c                           |  2 +
> > >  drivers/of/of_private.h                    |  2 +
> > >  drivers/of/of_reserved_mem.c               | 48 ++++++++++++++++++++
> > >  include/linux/crash_core.h                 |  2 +
> > >  include/linux/memblock.h                   |  9 ++++
> > >  include/linux/of_reserved_mem.h            |  1 +
> > >  kernel/crash_core.c                        | 51 ++++++++++++++++++++--
> > >  kernel/dma/contiguous.c                    |  1 +
> > >  mm/memblock.c                              | 17 ++++++++
> > >  14 files changed, 131 insertions(+), 95 deletions(-)
> > > 
> > 
> > 
> 
> -- 
> Sincerely yours,
> Mike.

  reply	other threads:[~2026-09-18  7:31 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02  7:31 Wandun Chen
2026-09-02  7:31 ` [PATCH v6 01/10] mm: memblock: add missing HugeTLB flag name Wandun Chen
2026-09-14  5:20   ` Mike Rapoport
2026-09-15 12:49     ` Wandun
2026-09-02  7:31 ` [PATCH v6 02/10] riscv: build crash_mem ranges from memblock instead of resource tree Wandun Chen
2026-09-02  7:31 ` [PATCH v6 03/10] crash_core: fold duplicated memblock arch hooks into the weak default Wandun Chen
2026-09-18  7:30   ` Baoquan He
2026-09-18  8:45     ` Wandun
2026-09-18  8:48       ` Baoquan He
2026-09-02  7:31 ` [PATCH v6 04/10] crash_core: serialize crash header preparation against hotplug Wandun Chen
2026-09-18  7:54   ` Baoquan He
2026-09-02  7:31 ` [PATCH v6 05/10] crash_core: replace for_each_mem_range() with for_each_mem_region() Wandun Chen
2026-09-18  8:04   ` Baoquan He
2026-09-02  7:31 ` [PATCH v6 06/10] memblock: introduce MEMBLOCK_NODUMP flag Wandun Chen
2026-09-18  7:00   ` Mike Rapoport
2026-09-18  8:08   ` Baoquan He
2026-09-18  8:22     ` Wandun
2026-09-02  7:31 ` [PATCH v6 07/10] of: reserved_mem: add dumpable flag to opt-in vmcore Wandun Chen
2026-09-17 21:56   ` Rob Herring (Arm)
2026-09-02  7:31 ` [PATCH v6 08/10] of: reserved_mem: mark /reserved-memory entries with MEMBLOCK_NODUMP Wandun Chen
2026-09-03  7:32   ` Marek Szyprowski
2026-09-17 21:56   ` Rob Herring (Arm)
2026-09-02  7:31 ` [PATCH v6 09/10] of: reserved_mem: mark /memreserve/ entries as MEMBLOCK_NODUMP Wandun Chen
2026-09-03  7:32   ` Marek Szyprowski
2026-09-02  7:31 ` [PATCH v6 10/10] crash_core: skip MEMBLOCK_NODUMP regions when building vmcore ELF header Wandun Chen
2026-09-18  8:09   ` Baoquan He
2026-09-02  8:53 ` [PATCH v6 00/10] kdump: reduce vmcore size and capture time Baoquan He
2026-09-03  7:05   ` Wandun
2026-09-03  7:31     ` Baoquan He
2026-09-03  7:43       ` Wandun
2026-09-03  9:38         ` Baoquan He
2026-09-04 11:08           ` Chen Wandun
2026-09-15 13:01 ` Wandun
2026-09-18  7:03   ` Mike Rapoport
2026-09-18  7:31     ` Baoquan He [this message]
2026-09-18  8:17 ` Baoquan He
2026-09-18 10:53   ` Wandun

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=aqzotDs4yDRxgcWS@fedora \
    --to=baoquan.he@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=chenhuacai@kernel.org \
    --cc=chenwandun1@gmail.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hpa@zytor.com \
    --cc=iommu@lists.linux.dev \
    --cc=kernel@xen0n.name \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=loongarch@lists.linux.dev \
    --cc=m.szyprowski@samsung.com \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=palmer@dabbelt.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=pjw@kernel.org \
    --cc=pratyush@kernel.org \
    --cc=robh@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=rppt@kernel.org \
    --cc=ruirui.yang@linux.dev \
    --cc=saravanak@kernel.org \
    --cc=tglx@kernel.org \
    --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

all inboxes | Powered by JetHome®