From: Chen Pei <cp0613@linux.alibaba.com>
To: rppt@kernel.org, pasha.tatashin@soleen.com, pratyush@kernel.org,
graf@amazon.com
Cc: kexec@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] kho: Skip zero-sized bootmem areas
Date: Mon, 26 Oct 2026 21:18:51 +0800 [thread overview]
Message-ID: <20261026131851.9942-1-cp0613@linux.alibaba.com> (raw)
The lowmem and the global bootmem area are reserved unconditionally,
while the per-node loop below already skips nodes whose size works out
to 0. Either can legitimately be 0: the global size is the scaled total
minus the lowmem one, so it is 0 whenever all measured reservations fit
below ARCH_LOW_ADDRESS_LIMIT.
Reserving 0 bytes still succeeds, so an area covering nothing gets
recorded with a valid address. That is not neutral:
kho_bootmem_overlap() reports an overlap for any request straddling
that address, and memblock_alloc_hugetlb() aligns a request to its page
size, so a 1G hugetlb allocation retries a free candidate on account of
an area that holds nothing.
A machine whose memory all starts at or above ARCH_LOW_ADDRESS_LIMIT
hits the other side of the same code: the lowmem size is 0, the range
below the limit is empty, the allocation fails and KHO is disabled
although no lowmem area was needed.
Skip a zero-sized area instead, as the per-node loop does. The
descriptor count stays consistent, as kho_populate() derives it from
the segment length that kho_fill_kimage() serialises.
Fixes: 3dc92c311498 ("kexec: add Kexec HandOver (KHO) generation helpers")
Signed-off-by: Chen Pei <cp0613@linux.alibaba.com>
---
kernel/liveupdate/kexec_handover.c | 38 +++++++++++++++++-------------
1 file changed, 21 insertions(+), 17 deletions(-)
diff --git a/kernel/liveupdate/kexec_handover.c b/kernel/liveupdate/kexec_handover.c
index 6f1f55fe3..c9c9fdfac 100644
--- a/kernel/liveupdate/kexec_handover.c
+++ b/kernel/liveupdate/kexec_handover.c
@@ -853,28 +853,32 @@ static void __init kho_reserve_bootmem(void)
* next kernel
*/
size = bootmem_size_lowmem;
- addr = memblock_phys_alloc_range(size, BOOTMEM_ALIGNMENT_BYTES, 0,
- ARCH_LOW_ADDRESS_LIMIT);
- if (!addr) {
- pr_err("Failed to reserve lowmem bootmem\n");
- goto err_free_bootmem_desc;
- }
+ if (size) {
+ addr = memblock_phys_alloc_range(size, BOOTMEM_ALIGNMENT_BYTES,
+ 0, ARCH_LOW_ADDRESS_LIMIT);
+ if (!addr) {
+ pr_err("Failed to reserve lowmem bootmem\n");
+ goto err_free_bootmem_desc;
+ }
- kho_bootmem[i].addr = addr;
- kho_bootmem[i].size = size;
- i++;
+ kho_bootmem[i].addr = addr;
+ kho_bootmem[i].size = size;
+ i++;
+ }
/* reserve large contiguous area for allocations without nid */
size = bootmem_size_global;
- addr = memblock_phys_alloc(size, BOOTMEM_ALIGNMENT_BYTES);
- if (!addr) {
- pr_err("Failed to reserve global bootmem\n");
- goto err_free_bootmem_areas;
- }
+ if (size) {
+ addr = memblock_phys_alloc(size, BOOTMEM_ALIGNMENT_BYTES);
+ if (!addr) {
+ pr_err("Failed to reserve global bootmem\n");
+ goto err_free_bootmem_areas;
+ }
- kho_bootmem[i].addr = addr;
- kho_bootmem[i].size = size;
- i++;
+ kho_bootmem[i].addr = addr;
+ kho_bootmem[i].size = size;
+ i++;
+ }
/*
* Loop over nodes that have both memory and are online. Skip
--
2.50.1
next reply other threads:[~2026-10-26 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 13:18 Chen Pei [this message]
2026-10-26 14:22 ` Pratyush Yadav
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=20261026131851.9942-1-cp0613@linux.alibaba.com \
--to=cp0613@linux.alibaba.com \
--cc=graf@amazon.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 \
/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®