[PATCH 1/4] kexec: do not place the next kernel in a fixed-address CMA area
sashiko-bot at kernel.org
sashiko-bot at kernel.org
Wed Nov 4 08:29:44 PST 2026
> kexec_alloc_contig() takes the next kernel's destination from the default
> CMA area and the next kernel runs from there in place, which is safe only
> if that area does not exist at the same address in the kernel being loaded.
> For a device-tree area it does: the loaded kernel declares the range it is
> executing from as a shared-dma-pool and cma_activate_area() frees its own
> image to the page allocator. Record in CMA_DYNAMIC_BASE which areas CMA
> placed itself and accept only those, letting kexec_locate_mem_hole() fall
> back to the memblock search. "cma=nn" works, "cma=nn at ss" no longer does.
>
> Fixes: 07d24902977e ("kexec: enable CMA based contiguous allocation")
> Suggested-by: Mike Rapoport <rppt at kernel.org>
> Signed-off-by: Radhey Shyam Pandey <radhey.shyam.pandey at amd.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261103162429.2053989-1-radhey.shyam.pandey@amd.com?part=1
More information about the kexec
mailing list