Re: [PATCH v2 03/32] kho: warn if KHO is disabled due to an error
From: Mike Rapoport <rppt@kernel.org>
Date: 2025-07-28 10:15:48
Also in:
linux-doc, linux-fsdevel, linux-mm, lkml
On Wed, Jul 23, 2025 at 02:46:16PM +0000, Pasha Tatashin wrote:
During boot scratch area is allocated based on command line parameters or auto calculated. However, scratch area may fail to allocate, and in that case KHO is disabled. Currently, no warning is printed that KHO is disabled, which makes it confusing for the end user to figure out why KHO is not available. Add the missing warning message. Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
quoted hunk ↗ jump to hunk
--- kernel/kexec_handover.c | 1 + 1 file changed, 1 insertion(+)diff --git a/kernel/kexec_handover.c b/kernel/kexec_handover.c index 1ff6b242f98c..368e23db0a17 100644 --- a/kernel/kexec_handover.c +++ b/kernel/kexec_handover.c@@ -565,6 +565,7 @@ static void __init kho_reserve_scratch(void) err_free_scratch_desc: memblock_free(kho_scratch, kho_scratch_cnt * sizeof(*kho_scratch)); err_disable_kho: + pr_warn("Failed to reserve scratch area, disabling kexec handover\n"); kho_enable = false; }-- 2.50.0.727.gbf7dc18ff4-goog
-- Sincerely yours, Mike.