From nobody Wed Dec 17 01:25:28 2025 Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [45.249.212.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DBC5D1396 for ; Mon, 22 Jul 2024 03:52:10 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.249.212.187 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1721620333; cv=none; b=uRH92JgVMhsH+oLzd85n2GT6TuRbvkiSgRuOzWoqlaYjwlnHPH4hD7NMPiepHjaBYyWskJ/LI8wCIdQsKglLFf3SqZrRZoTInC4qqFAgKYZCmAXunZTxXCR6WVPqtvxhQadpyF071a1f7V0e4sIR5M9YvKkvsyjFioUhFllvjTU= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1721620333; c=relaxed/simple; bh=pUz3zsNSoTxp0DNINxVoUjmyY0qseumNHFhL23K9Nys=; h=From:To:CC:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=A1lVpET0QRN5bO692cU9/YgX6uZQNV5KVGu3CKklUTL/so1lFbF0J9gKJQ7fwAABeiwrJTZohtt/5WopN2C4KtrVpAWXuC0pgaOst+YwmdwKfHHFH2trPcFS0/c3jb2UzD8Um4vb3jnFszMclFVyvDNFglJ5CBGvmviNfr0yi9E= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; arc=none smtp.client-ip=45.249.212.187 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Received: from mail.maildlp.com (unknown [172.19.163.252]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4WS5nT6nVKzxSQm; Mon, 22 Jul 2024 11:47:09 +0800 (CST) Received: from kwepemi100008.china.huawei.com (unknown [7.221.188.57]) by mail.maildlp.com (Postfix) with ESMTPS id 1B0721800A1; Mon, 22 Jul 2024 11:52:08 +0800 (CST) Received: from huawei.com (10.90.53.73) by kwepemi100008.china.huawei.com (7.221.188.57) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Mon, 22 Jul 2024 11:52:07 +0800 From: Jinjie Ruan To: , , , , , , , , , , , , , , , , , , , , , , , , , , CC: Subject: [PATCH v4 1/3] x86/kexec: Fix crash memory reserve exceed system memory bug Date: Mon, 22 Jul 2024 11:56:59 +0800 Message-ID: <20240722035701.696874-2-ruanjinjie@huawei.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20240722035701.696874-1-ruanjinjie@huawei.com> References: <20240722035701.696874-1-ruanjinjie@huawei.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-ClientProxiedBy: dggems704-chm.china.huawei.com (10.3.19.181) To kwepemi100008.china.huawei.com (7.221.188.57) Content-Type: text/plain; charset="utf-8" On x86_32 Qemu machine with 1GB memory, the cmdline "crashkernel=3D4G" is ok as below: crashkernel reserved: 0x0000000020000000 - 0x0000000120000000 (4096 MB) The cause is that the crash_size is parsed and printed with "unsigned long long" data type which is 8 bytes but allocated used with "phys_addr_t" which is 4 bytes in memblock_phys_alloc_range(). Fix it by checking if the crash_size is greater than system RAM size and warn out as parse_crashkernel_mem() do it if so as Baoquan suggested. After this patch, it fails and there is no above confusing reserve success info. Signed-off-by: Jinjie Ruan Suggested-by: Baoquan He --- v4: - Update the warn info to align with parse_crashkernel_mem(). - Update the commit message. v3: - Handle the check in arch_reserve_crashkernel() Baoquan suggested. - Split x86_32 and arm32. - Add Suggested-by. - Drop the wrong fix tag. v2: - Also fix for x86_32. - Update the fix method. - Peel off the other two patches. - Update the commit message. --- arch/x86/kernel/setup.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c index 5d34cad9b7b1..77b937dbd98c 100644 --- a/arch/x86/kernel/setup.c +++ b/arch/x86/kernel/setup.c @@ -482,6 +482,11 @@ static void __init arch_reserve_crashkernel(void) if (ret) return; =20 + if (crash_size >=3D memblock_phys_mem_size()) { + pr_warn("Crashkernel: invalid size."); + return; + } + if (xen_pv_domain()) { pr_info("Ignoring crashkernel for a Xen PV domain\n"); return; --=20 2.34.1