[PATCH] kho: do not reserve empty per-node bootmem areas
Mike Rapoport
rppt at kernel.org
Thu Oct 15 01:39:34 PDT 2026
From: Mike Rapoport (Microsoft) <rppt at kernel.org>
On Wed, 14 Oct 2026 15:15:44 +0200, Pratyush Yadav wrote:
> Some nodes do not allocate any early boot memory. An example is
> hotpluggable nodes with movable_node enabled. So the scratch size for
> them ends up being zero. Zero size allocations normally don't play well
> with memblock. Memblock returns an address, but then doesn't actually
> reserve anything. This address ends up being recorded in kho_bootmem
> with a size of 0. In case of hotpluggable nodes with movable_nodes, the
> allocation on the node actually fails because memblock refuses to
> allocate there, and so KHO fails to initialize.
>
> [...]
Applied to next branch of liveupdate/linux.git tree, thanks!
[1/1] kho: do not reserve empty per-node bootmem areas
commit: 9a6a70aefe77f6fb9ff2b3037dcf87f6dff65c8c
tree: https://git.kernel.org/pub/scm/linux/kernel/git/liveupdate/linux
branch: next
--
Sincerely yours,
Mike.
More information about the kexec
mailing list