[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240708133348.3592667-3-ruanjinjie@huawei.com>
Date: Mon, 8 Jul 2024 21:33:47 +0800
From: Jinjie Ruan <ruanjinjie@...wei.com>
To: <linux@...linux.org.uk>, <bhe@...hat.com>, <vgoyal@...hat.com>,
<dyoung@...hat.com>, <paul.walmsley@...ive.com>, <palmer@...belt.com>,
<aou@...s.berkeley.edu>, <arnd@...db.de>, <afd@...com>,
<akpm@...ux-foundation.org>, <rmk+kernel@...linux.org.uk>,
<linus.walleij@...aro.org>, <eric.devolder@...cle.com>,
<gregkh@...uxfoundation.org>, <deller@....de>, <javierm@...hat.com>,
<robh@...nel.org>, <thunder.leizhen@...wei.com>, <austindh.kim@...il.com>,
<linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
<kexec@...ts.infradead.org>
CC: <ruanjinjie@...wei.com>
Subject: [PATCH 2/3] ARM: Fix crash kenrel data type bug
On QEMU vexpress-a9 with 1GB memory, the crash kernel "crashkernel=4G"
is ok as below:
Reserving 4096MB of memory at 2432MB for crashkernel (System RAM: 1024MB)
The above info is confusing, because the System memory is as below:
# cat /proc/iomem | grep Sys
60000000-9fffffff : System RAM
The cause is that the crash_size is parsed and printed with "unsigned long
long" data type which is 8 bytes but used with "phys_addr_t" which is
4 bytes in memblock_phys_alloc_range().
Fixes: 9d17f3372306 ("ARM: 9190/1: kdump: add invalid input check for 'crashkernel=0'")
Signed-off-by: Jinjie Ruan <ruanjinjie@...wei.com>
---
arch/arm/kernel/setup.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/kernel/setup.c b/arch/arm/kernel/setup.c
index e6a857bf0ce6..59e1a13b5cf6 100644
--- a/arch/arm/kernel/setup.c
+++ b/arch/arm/kernel/setup.c
@@ -1012,6 +1012,7 @@ static void __init reserve_crashkernel(void)
&crash_size, &crash_base,
NULL, NULL);
/* invalid value specified or crashkernel=0 */
+ crash_size = (phys_addr_t)crash_size;
if (ret || !crash_size)
return;
--
2.34.1
Powered by blists - more mailing lists