From: sashiko-bot@kernel.org
To: "Pufan Jin" <cyan2254650260@gmail.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v3 3/3] arm64: zynqmp: Add ALINX EdgeBoard FZ3A
Date: Wed, 14 Oct 2026 18:10:14 +0000 [thread overview]
Message-ID: <sashiko-outbox-171668@kernel.org> (raw)
In-Reply-To: <20261014175020.62907-4-cyan2254650260@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] dts: memory corruption due to memory@0 truncation without reserved-memory
--
commit 47a176ea68469cbcbe7f485f00a695a0a5b3915f
Author: Pufan Jin <cyan2254650260@gmail.com>
arm64: zynqmp: Add ALINX EdgeBoard FZ3A
Add device tree for the ALINX EdgeBoard FZ3A, a single board computer
based on the Xilinx Zynq UltraScale+ XCZU3EG SoC.
Link: https://ai.baidu.com/tech/hardware/deepkit
Link: https://ai.baidu.com/ai-doc/HWCE/8kq9b2121
Link: https://www.alinx.com/
> diff --git a/arch/arm64/boot/dts/xilinx/zynqmp-alinx-edgeboard-fz3a.dts b/arch/arm64/boot/dts/xilinx/zynqmp-alinx-edgeboard-fz3a.dts
> new file mode 100644
> index 0000000000000..6cad90091a4c9
> --- /dev/null
> +++ b/arch/arm64/boot/dts/xilinx/zynqmp-alinx-edgeboard-fz3a.dts
[ ... ]
> + reserved_memory: reserved-memory {
> + ranges;
> + #address-cells = <2>;
> + #size-cells = <2>;
> +
> + linux_cma: cma {
> + compatible = "shared-dma-pool";
> + alloc-ranges = <0x0 0x0 0x0 0x7ff00000>;
> + reusable;
> + size = <0x0 0x20000000>;
> + };
> + };
> +
> + memory@0 {
> + device_type = "memory";
> + reg = <0x0 0x0 0x0 0x7ff00000>;
> + };
[Severity: High]
Does this truncated memory range safely protect firmware memory from Linux?
ZynqMP U-Boot typically features automatic memory fixups
(fdt_fixup_memory_banks) which overwrite the reg property of memory@0 to
the full hardware-detected DDR size before booting Linux.
Since the device tree lacks a corresponding reserved-memory node with
no-map for this 1MB region, Linux might see the U-Boot expanded memory
range, map the entire memory, and allocate from the firmware's region,
potentially leading to memory corruption or boot crashes.
Should this firmware region be explicitly reserved using a reserved-memory
child node with no-map instead?
> +};
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261014175020.62907-1-cyan2254650260@gmail.com?part=3
prev parent reply other threads:[~2026-10-14 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 17:50 [PATCH v3 0/3] arm64: zynqmp: Add support for ALINX EdgeBoard FZ3A Pufan Jin
2026-10-14 17:50 ` [PATCH v3 1/3] dt-bindings: vendor-prefixes: Add ALINX vendor prefix Pufan Jin
2026-10-14 17:50 ` [PATCH v3 2/3] dt-bindings: soc: xilinx: Add ALINX EdgeBoard FZ3A Pufan Jin
2026-10-14 17:50 ` [PATCH v3 3/3] arm64: zynqmp: " Pufan Jin
2026-10-14 18:10 ` sashiko-bot [this message]
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=sashiko-outbox-171668@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cyan2254650260@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox