From: Hanjun Guo <guohanjun@huawei.com>
To: Will Deacon <will@kernel.org>, Pengpeng Hou <pengpeng@iscas.ac.cn>
Cc: Lorenzo Pieralisi <lpieralisi@kernel.org>,
Sudeep Holla <sudeep.holla@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, <linux-acpi@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI: IORT: validate RMR node array bounds
Date: Tue, 4 Aug 2026 11:40:50 +0800 [thread overview]
Message-ID: <65d0a7d6-c71b-d779-4b95-85fcd3495195@huawei.com> (raw)
In-Reply-To: <amzCci9-3kMZbSI4@google.com>
Hi Will,
On 2026/7/31 23:42, Will Deacon wrote:
> On Mon, Jul 06, 2026 at 05:43:00PM +0800, Pengpeng Hou wrote:
>> IORT RMR nodes describe reserved-memory ranges through firmware
>> offset and count fields inside the current IORT node.
>>
>> Validate the generic IORT node length before dispatching it, and
>> check both the RMR descriptor array and the ID mapping array before
>> walking them. This binds each array walk to the current node length
>> instead of only trusting the firmware-provided count.
>>
>> Signed-off-by: Pengpeng Hou <pengpeng@iscas.ac.cn>
>> ---
>> drivers/acpi/arm64/iort.c | 83 +++++++++++++++++++++++++++++++++++++--
>> 1 file changed, 79 insertions(+), 4 deletions(-)
>
> Hanjun, Lorenzo, any thoughts on this one?
Thanks for reminding.
In my personal opinion, this is not a real issue because if something
wrong with the IORT, the IORT will not work at booting, for example
the device will map to a wrong ITS or SMMU, the device will not work
at all, so those issues will be fixed at the pre-production stage,
correct me if I'm wrong.
But to the patch itself, it's no harm, I will comment on this patch.
Thanks
Hanjun
next prev parent reply other threads:[~2026-08-04 3:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 9:43 [PATCH] ACPI: IORT: validate RMR node array bounds Pengpeng Hou
2026-07-31 15:42 ` Will Deacon
2026-08-04 3:40 ` Hanjun Guo [this message]
2026-08-04 7:07 ` Hanjun Guo
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=65d0a7d6-c71b-d779-4b95-85fcd3495195@huawei.com \
--to=guohanjun@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=pengpeng@iscas.ac.cn \
--cc=rafael@kernel.org \
--cc=sudeep.holla@kernel.org \
--cc=will@kernel.org \
/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