From: Baoquan He <bhe@redhat.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: vgoyal@redhat.com, dyoung@redhat.com, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, rppt@kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5] crash: Fix crash memory reserve exceed system memory bug
Date: Tue, 23 Jul 2024 13:17:27 +0800 [thread overview]
Message-ID: <Zp8859QW+YV1KqQ9@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20240723020746.3945016-1-ruanjinjie@huawei.com>
On 07/23/24 at 10:07am, Jinjie Ruan wrote:
> On x86_32 Qemu machine with 1GB memory, the cmdline "crashkernel=4G" is ok
> as below:
> crashkernel reserved: 0x0000000020000000 - 0x0000000120000000 (4096 MB)
>
> It's similar on other architectures, such as ARM32 and RISCV32.
>
> 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 crash_size is greater than system RAM size and
> return error if so.
>
> After this patch, there is no above confusing reserve success info.
>
> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
> Suggested-by: Baoquan He <bhe@redhat.com>
> Suggested-by: Mike Rapoport <rppt@kernel.org>
My Suggested-by can be taken off because I suggested to check the parsed
value after parse_crashkernel(), Mike's suggestion is better.
For this version,
Acked-by: Baoquan He <bhe@redhat.com>
> ---
> v5:
> - Fix it in common parse_crashkernel() instead of per-arch.
> - Add suggested-by.
>
> v4:
> - Update the warn info to align with parse_crashkernel_mem().
> - Rebased on the "ARM: Use generic interface to simplify crashkernel
> reservation" patch.
> - Also fix for riscv32.
> - Update the commit message.
>
> v3:
> - Handle the check in 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.
> ---
> kernel/crash_reserve.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/kernel/crash_reserve.c b/kernel/crash_reserve.c
> index ad5b3f2c5487..5387269114f6 100644
> --- a/kernel/crash_reserve.c
> +++ b/kernel/crash_reserve.c
> @@ -335,6 +335,9 @@ int __init parse_crashkernel(char *cmdline,
> if (!*crash_size)
> ret = -EINVAL;
>
> + if (*crash_size >= system_ram)
> + ret = -EINVAL;
> +
> return ret;
> }
>
> --
> 2.34.1
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: vgoyal@redhat.com, dyoung@redhat.com, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, rppt@kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5] crash: Fix crash memory reserve exceed system memory bug
Date: Tue, 23 Jul 2024 13:17:27 +0800 [thread overview]
Message-ID: <Zp8859QW+YV1KqQ9@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20240723020746.3945016-1-ruanjinjie@huawei.com>
On 07/23/24 at 10:07am, Jinjie Ruan wrote:
> On x86_32 Qemu machine with 1GB memory, the cmdline "crashkernel=4G" is ok
> as below:
> crashkernel reserved: 0x0000000020000000 - 0x0000000120000000 (4096 MB)
>
> It's similar on other architectures, such as ARM32 and RISCV32.
>
> 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 crash_size is greater than system RAM size and
> return error if so.
>
> After this patch, there is no above confusing reserve success info.
>
> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
> Suggested-by: Baoquan He <bhe@redhat.com>
> Suggested-by: Mike Rapoport <rppt@kernel.org>
My Suggested-by can be taken off because I suggested to check the parsed
value after parse_crashkernel(), Mike's suggestion is better.
For this version,
Acked-by: Baoquan He <bhe@redhat.com>
> ---
> v5:
> - Fix it in common parse_crashkernel() instead of per-arch.
> - Add suggested-by.
>
> v4:
> - Update the warn info to align with parse_crashkernel_mem().
> - Rebased on the "ARM: Use generic interface to simplify crashkernel
> reservation" patch.
> - Also fix for riscv32.
> - Update the commit message.
>
> v3:
> - Handle the check in 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.
> ---
> kernel/crash_reserve.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/kernel/crash_reserve.c b/kernel/crash_reserve.c
> index ad5b3f2c5487..5387269114f6 100644
> --- a/kernel/crash_reserve.c
> +++ b/kernel/crash_reserve.c
> @@ -335,6 +335,9 @@ int __init parse_crashkernel(char *cmdline,
> if (!*crash_size)
> ret = -EINVAL;
>
> + if (*crash_size >= system_ram)
> + ret = -EINVAL;
> +
> return ret;
> }
>
> --
> 2.34.1
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: vgoyal@redhat.com, dyoung@redhat.com, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, rppt@kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5] crash: Fix crash memory reserve exceed system memory bug
Date: Tue, 23 Jul 2024 13:17:27 +0800 [thread overview]
Message-ID: <Zp8859QW+YV1KqQ9@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20240723020746.3945016-1-ruanjinjie@huawei.com>
On 07/23/24 at 10:07am, Jinjie Ruan wrote:
> On x86_32 Qemu machine with 1GB memory, the cmdline "crashkernel=4G" is ok
> as below:
> crashkernel reserved: 0x0000000020000000 - 0x0000000120000000 (4096 MB)
>
> It's similar on other architectures, such as ARM32 and RISCV32.
>
> 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 crash_size is greater than system RAM size and
> return error if so.
>
> After this patch, there is no above confusing reserve success info.
>
> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
> Suggested-by: Baoquan He <bhe@redhat.com>
> Suggested-by: Mike Rapoport <rppt@kernel.org>
My Suggested-by can be taken off because I suggested to check the parsed
value after parse_crashkernel(), Mike's suggestion is better.
For this version,
Acked-by: Baoquan He <bhe@redhat.com>
> ---
> v5:
> - Fix it in common parse_crashkernel() instead of per-arch.
> - Add suggested-by.
>
> v4:
> - Update the warn info to align with parse_crashkernel_mem().
> - Rebased on the "ARM: Use generic interface to simplify crashkernel
> reservation" patch.
> - Also fix for riscv32.
> - Update the commit message.
>
> v3:
> - Handle the check in 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.
> ---
> kernel/crash_reserve.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/kernel/crash_reserve.c b/kernel/crash_reserve.c
> index ad5b3f2c5487..5387269114f6 100644
> --- a/kernel/crash_reserve.c
> +++ b/kernel/crash_reserve.c
> @@ -335,6 +335,9 @@ int __init parse_crashkernel(char *cmdline,
> if (!*crash_size)
> ret = -EINVAL;
>
> + if (*crash_size >= system_ram)
> + ret = -EINVAL;
> +
> return ret;
> }
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-07-23 5:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 2:07 [PATCH v5] crash: Fix crash memory reserve exceed system memory bug Jinjie Ruan
2024-07-23 2:07 ` Jinjie Ruan
2024-07-23 2:07 ` Jinjie Ruan
2024-07-23 5:17 ` Baoquan He [this message]
2024-07-23 5:17 ` Baoquan He
2024-07-23 5:17 ` Baoquan He
2024-07-29 3:24 ` Jinjie Ruan
2024-07-29 3:24 ` Jinjie Ruan
2024-07-29 3:24 ` Jinjie Ruan
2024-07-29 3:29 ` Baoquan He
2024-07-29 3:29 ` Baoquan He
2024-07-29 3:29 ` Baoquan He
2024-07-29 11:28 ` Jinjie Ruan
2024-07-29 11:28 ` Jinjie Ruan
2024-07-29 11:28 ` Jinjie Ruan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zp8859QW+YV1KqQ9@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=aou@eecs.berkeley.edu \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rppt@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=vgoyal@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.