From: Jiri Bohac <jbohac@suse.cz>
To: Mikhail Zaslonko <zaslonko@linux.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <baoquan.he@linux.dev>,
Mike Rapoport <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
Dave Young <ruirui.yang@linux.dev>,
David Hildenbrand <david@kernel.org>,
Usama Arif <usama.arif@linux.dev>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
kexec@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kdump: Give crashkernel CMA areas unique names
Date: Fri, 6 Nov 2026 15:13:50 +0100 [thread overview]
Message-ID: <au3gnsckVTK6tUs5@dwarf.suse.cz> (raw)
In-Reply-To: <20261106104309.3669583-1-zaslonko@linux.ibm.com>
On Fri, Nov 06, 2026 at 11:43:09AM +0100, Mikhail Zaslonko wrote:
> reserve_crashkernel_cma() names every CMA area it reserves
> "crashkernel". If the requested size can't be reserved in one piece,
> it falls back to several smaller areas, all with the same name.
> With CONFIG_CMA_SYSFS, cma_sysfs_init() then fails to create the second
> directory:
>
> sysfs: cannot create duplicate filename '/kernel/mm/cma/crashkernel'
>
> and the error path removes the sysfs entries of all CMA areas.
>
> With CONFIG_CMA_DEBUGFS, debugfs refuses the duplicate directories as
> well:
>
> debugfs: 'crashkernel' already exists in 'cma'
>
> so only the first area shows up in debugfs.
>
> Keep the name of the first area and add the index to the others:
> crashkernel, crashkernel1, crashkernel2, ...
>
> Fixes: ab475510e042 ("kdump: implement reserve_crashkernel_cma")
> Signed-off-by: Mikhail Zaslonko <zaslonko@linux.ibm.com>
Thanks for fixing this.
I don't think we really need the special case for crashk_cma_cnt == 0
and that "crashkernel0" would be fine. But I don't mind either way.
Acked-by: Jiri Bohac <jbohac@suse.cz>
--
Jiri Bohac <jbohac@suse.cz>
SUSE Labs, Prague, Czechia
prev parent reply other threads:[~2026-11-06 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 10:43 Mikhail Zaslonko
2026-11-06 12:38 ` David Hildenbrand (Arm)
2026-11-06 13:50 ` Usama Arif
2026-11-06 14:13 ` Jiri Bohac [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=au3gnsckVTK6tUs5@dwarf.suse.cz \
--to=jbohac@suse.cz \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=baoquan.he@linux.dev \
--cc=david@kernel.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=ruirui.yang@linux.dev \
--cc=usama.arif@linux.dev \
--cc=zaslonko@linux.ibm.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
all inboxes | Powered by JetHome®