From: David Hildenbrand <dhildenb@redhat.com>
To: Breno Leitao <leitao@debian.org>, Jiri Bohac <jbohac@suse.cz>
Cc: riel@surriel.com, vbabka@suse.cz, nphamcs@gmail.com,
Baoquan He <bhe@redhat.com>, Vivek Goyal <vgoyal@redhat.com>,
Dave Young <dyoung@redhat.com>,
kexec@lists.infradead.org, akpm@linux-foundation.org,
Philipp Rudo <prudo@redhat.com>,
Donald Dutile <ddutile@redhat.com>,
Pingfan Liu <piliu@redhat.com>, Tao Liu <ltao@redhat.com>,
linux-kernel@vger.kernel.org, Michal Hocko <mhocko@suse.cz>
Subject: Re: [PATCH v5 0/5] kdump: crashkernel reservation from CMA
Date: Mon, 6 Oct 2025 10:16:26 +0200 [thread overview]
Message-ID: <26ae6b04-3beb-47e9-9639-b081003dc9bb@redhat.com> (raw)
In-Reply-To: <vojlxf5pelxlr6omsfsccd4e4cdzn5qyxpgiqajorkgmgd7ruh@e5wwhkmvntpb>
On 03.10.25 17:51, Breno Leitao wrote:
> Hello Jiri,
>
> On Thu, Jun 12, 2025 at 12:11:19PM +0200, Jiri Bohac wrote:
>
>> Currently this is only the case for memory ballooning and zswap. Such movable
>> memory will be missing from the vmcore. User data is typically not dumped by
>> makedumpfile.
>
> For zswap and zsmalloc pages, I'm wondering whether these pages will be missing
> from the vmcore, or if there's a possibility they might be present but
> corrupted—especially since they could reside in the CMA region, which may be
> overwritten by the kdump environment.
That's not different to ordinary user pages residing on these areas, right?
--
Cheers
David / dhildenb
next prev parent reply other threads:[~2025-10-06 8:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 10:11 [PATCH v5 0/5] kdump: crashkernel reservation from CMA Jiri Bohac
2025-06-12 10:13 ` [PATCH v5 1/5] Add a new optional ",cma" suffix to the crashkernel= command line option Jiri Bohac
2025-06-12 10:16 ` [PATCH v5 2/5] kdump: implement reserve_crashkernel_cma Jiri Bohac
2025-06-12 10:17 ` [PATCH v5 3/5] kdump, documentation: describe craskernel CMA reservation Jiri Bohac
2025-06-12 10:18 ` [PATCH v5 4/5] kdump: wait for DMA to finish when using CMA Jiri Bohac
2025-06-12 23:47 ` Andrew Morton
2025-06-13 9:19 ` David Hildenbrand
2025-06-14 2:41 ` Baoquan He
2025-06-19 12:46 ` Jiri Bohac
2025-06-12 10:20 ` [PATCH v5 5/5] x86: implement crashkernel cma reservation Jiri Bohac
2025-08-20 15:46 ` [PATCH v5 0/5] kdump: crashkernel reservation from CMA Breno Leitao
2025-08-20 16:20 ` Jiri Bohac
2025-08-21 8:35 ` Breno Leitao
2025-08-22 19:45 ` Jiri Bohac
2025-10-03 15:51 ` Breno Leitao
2025-10-06 8:16 ` David Hildenbrand [this message]
2025-10-06 16:25 ` Breno Leitao
2025-10-06 16:45 ` David Hildenbrand
2025-10-06 23:34 ` Tao Liu
2025-10-07 3:55 ` Baoquan He
2025-10-07 9:11 ` Jiri Bohac
2025-10-08 10:42 ` Breno Leitao
2025-10-13 4:03 ` [External] " Zhongkun He
2025-10-13 8:00 ` David Hildenbrand
2025-10-14 7:36 ` Zhongkun He
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=26ae6b04-3beb-47e9-9639-b081003dc9bb@redhat.com \
--to=dhildenb@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=ddutile@redhat.com \
--cc=dyoung@redhat.com \
--cc=jbohac@suse.cz \
--cc=kexec@lists.infradead.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltao@redhat.com \
--cc=mhocko@suse.cz \
--cc=nphamcs@gmail.com \
--cc=piliu@redhat.com \
--cc=prudo@redhat.com \
--cc=riel@surriel.com \
--cc=vbabka@suse.cz \
--cc=vgoyal@redhat.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