From: Mark Brown <broonie@kernel.org>
To: Mike Rapoport <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>
Cc: David Hildenbrand <david@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Mikhail Zaslonko <zaslonko@linux.ibm.com>,
Usama Arif <usama.arif@linux.dev>,
Vlastimil Babka <vbabka@kernel.org>
Subject: linux-next: manual merge of the kexec tree with the mm tree
Date: Mon, 16 Nov 2026 19:25:56 +0000 [thread overview]
Message-ID: <avtYxJJhIzPVDYVv@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]
Hi all,
Today's linux-next merge of the kexec tree got a conflict in:
kernel/crash_reserve.c
between commit:
ed27d3cb114dd ("mm/hugetlb: allow crashkernel to reuse hugetlb CMA memory")
from the mm tree and commit:
941aef93e9e1d ("kdump: Give crashkernel CMA areas unique names")
from the kexec tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
diff --cc kernel/crash_reserve.c
index 53d76ba6b3c31,80092c86d586a..0000000000000
--- a/kernel/crash_reserve.c
+++ b/kernel/crash_reserve.c
@@@ -503,11 -483,16 +503,17 @@@ void __init reserve_crashkernel_cma(voi
while (cma_size > reserved_size &&
crashk_cma_cnt < CRASHKERNEL_CMA_RANGES_MAX) {
+ char name[CMA_MAX_NAME];
struct cma *res;
+ request_size = min(request_size, cma_size - reserved_size);
+ /* CMA area names show up in sysfs and debugfs, keep them unique */
+ if (crashk_cma_cnt)
+ snprintf(name, sizeof(name), "crashkernel%d", crashk_cma_cnt);
+ else
+ strscpy(name, "crashkernel");
if (cma_declare_contiguous(0, request_size, 0, 0, 0, false,
- "crashkernel", &res)) {
+ name, &res)) {
/* reservation failed, try half-sized blocks */
if (request_size <= PAGE_SIZE)
break;
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-11-16 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 19:25 Mark Brown [this message]
2026-11-16 19:42 ` Andrew Morton
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=avtYxJJhIzPVDYVv@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
--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®