From: sashiko-bot@kernel.org
To: "Wandun Chen" <chenwandun1@gmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v4 03/10] of: reserved_mem: skip late scan when no regions are reserved
Date: Tue, 30 Jun 2026 08:19:36 +0000 [thread overview]
Message-ID: <20260630081937.3F4091F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260630074715.4126796-4-chenwandun1@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] The `dynamic_nodes` array in `fdt_scan_reserved_mem()` has a fixed size of `MAX_RESERVED_REGIONS` (64) but lacks bounds checking, leading to a potential stack buffer overflow.
--
commit e62a55f3fff119a2e88f5aefe6dbf1cf5ef32c31
Author: Wandun Chen <chenwandun@lixiang.com>
of: reserved_mem: skip late scan when no regions are reserved
This commit optimizes reserved memory initialization by skipping the
late scan when no reserved regions exist. It updates
alloc_reserved_mem_array() to return -ENODEV directly if
total_reserved_mem_cnt is 0.
> diff --git a/drivers/of/of_reserved_mem.c b/drivers/of/of_reserved_mem.c
> index 42649dc3613f0..e1bd35115cc1e 100644
> --- a/drivers/of/of_reserved_mem.c
> +++ b/drivers/of/of_reserved_mem.c
> @@ -76,7 +76,7 @@ static int __init alloc_reserved_mem_array(void)
> int ret;
>
> if (!total_reserved_mem_cnt)
> - return 0;
> + return -ENODEV;
>
> alloc_size = array_size(total_reserved_mem_cnt, sizeof(*new_array));
[Severity: High]
This isn't a bug introduced by this patch, but while reviewing the reserved
memory changes, I noticed a potential issue in the nearby
fdt_scan_reserved_mem() function.
Does this code overflow dynamic_nodes[] if the device tree contains more
than MAX_RESERVED_REGIONS dynamic regions?
drivers/of/of_reserved_mem.c:fdt_scan_reserved_mem() {
int dynamic_nodes_cnt = 0;
int dynamic_nodes[MAX_RESERVED_REGIONS];
...
if (err == -ENOENT && of_get_flat_dt_prop(child, "size", NULL)) {
dynamic_nodes[dynamic_nodes_cnt] = child;
dynamic_nodes_cnt++;
}
...
}
If a malformed Flattened Device Tree is provided with more than 64 dynamically
allocated reserved memory regions, it looks like dynamic_nodes_cnt could
increment past the bounds of the array, leading to stack corruption.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260630074715.4126796-1-chenwandun1@gmail.com?part=3
next prev parent reply other threads:[~2026-06-30 8:19 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 7:47 [PATCH v4 00/10] kdump: reduce vmcore size and capture time Wandun Chen
2026-06-30 7:47 ` Wandun Chen
2026-06-30 7:47 ` [PATCH v4 01/10] kexec/crash: provide crash_exclude_mem_range() stub when CONFIG_CRASH_DUMP=n Wandun Chen
2026-06-30 7:47 ` Wandun Chen
2026-06-30 11:05 ` Pratyush Yadav
2026-06-30 11:05 ` Pratyush Yadav
2026-06-30 7:47 ` [PATCH v4 02/10] of: reserved_mem: dedup and relocate reserved-memory messages Wandun Chen
2026-06-30 7:47 ` Wandun Chen
2026-06-30 7:47 ` [PATCH v4 03/10] of: reserved_mem: skip late scan when no regions are reserved Wandun Chen
2026-06-30 7:47 ` Wandun Chen
2026-06-30 8:19 ` sashiko-bot [this message]
2026-06-30 7:47 ` [PATCH v4 04/10] of: reserved_mem: split alloc_reserved_mem_array() from fdt_scan_reserved_mem_late() Wandun Chen
2026-06-30 7:47 ` Wandun Chen
2026-06-30 7:47 ` [PATCH v4 05/10] of: reserved_mem: add dumpable flag to opt-in vmcore Wandun Chen
2026-06-30 7:47 ` Wandun Chen
2026-06-30 7:47 ` [PATCH v4 06/10] of: reserved_mem: save /memreserve/ entries into the reserved_mem array Wandun Chen
2026-06-30 7:47 ` Wandun Chen
2026-06-30 7:47 ` [PATCH v4 07/10] of: reserved_mem: add kdump helpers to exclude non-dumpable regions Wandun Chen
2026-06-30 7:47 ` Wandun Chen
2026-06-30 11:06 ` Pratyush Yadav
2026-06-30 11:06 ` Pratyush Yadav
2026-06-30 7:47 ` [PATCH v4 08/10] arm64: kdump: exclude non-dumpable reserved memory regions from vmcore Wandun Chen
2026-06-30 7:47 ` Wandun Chen
2026-06-30 9:04 ` sashiko-bot
2026-06-30 11:06 ` Pratyush Yadav
2026-06-30 11:06 ` Pratyush Yadav
2026-06-30 7:47 ` [PATCH v4 09/10] riscv: " Wandun Chen
2026-06-30 7:47 ` Wandun Chen
2026-06-30 9:22 ` sashiko-bot
2026-06-30 11:12 ` Pratyush Yadav
2026-06-30 11:12 ` Pratyush Yadav
2026-06-30 12:00 ` Wandun
2026-06-30 12:00 ` Wandun
2026-06-30 7:47 ` [PATCH v4 10/10] loongarch: " Wandun Chen
2026-06-30 7:47 ` Wandun Chen
2026-06-30 9:37 ` sashiko-bot
2026-06-30 11:13 ` Pratyush Yadav
2026-06-30 11:13 ` Pratyush Yadav
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=20260630081937.3F4091F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=chenwandun1@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.