[<prev] [next>] [day] [month] [year] [list]
Message-ID: <aYVvieviDNvoTRNq@adminpc-PowerEdge-R7525>
Date: Fri, 6 Feb 2026 13:35:21 +0900
From: Austin Kim <austindh.kim@...il.com>
To: Paul Walmsley <pjw@...nel.org>, Palmer Dabbelt <palmer@...belt.com>,
Alexandre Ghiti <alex@...ti.fr>
Cc: linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org,
austindh.kim@...il.com
Subject: [PATCH] riscv: kdump: return early for invalid 'crashkernel=0' input
From: Austin Kim <austin.kim@....com>
An invalid 'crashkernel=0' can be specified when running kdump.
By adding a check for 'crashkernel=0', it can return early when detecting
this invalid input.
Signed-off-by: Austin Kim <austin.kim@....com>
---
arch/riscv/mm/init.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/riscv/mm/init.c b/arch/riscv/mm/init.c
index 811e03786..e61fec445 100644
--- a/arch/riscv/mm/init.c
+++ b/arch/riscv/mm/init.c
@@ -1409,7 +1409,8 @@ static void __init arch_reserve_crashkernel(void)
ret = parse_crashkernel(boot_command_line, memblock_phys_mem_size(),
&crash_size, &crash_base,
&low_size, NULL, &high);
- if (ret)
+ /* invalid value specified or 'crashkernel=0' */
+ if (ret || !crash_size)
return;
reserve_crashkernel_generic(crash_size, crash_base, low_size, high);
--
2.34.1
Powered by blists - more mailing lists