From: Lizhi Hou <lizhi.hou@amd.com>
To: Taimuraz Kaitmazov <taimuraz@kaitmazov.com>, <mamin506@gmail.com>,
<ogabbay@kernel.org>
Cc: <dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] accel/amdxdna: reject a command chain that carries no commands
Date: Mon, 24 Aug 2026 09:40:49 -0700 [thread overview]
Message-ID: <c66806ab-9944-0524-c36a-688dc0f05641@amd.com> (raw)
In-Reply-To: <21089f21-ba36-69eb-2b9c-642fb0ab1498@amd.com>
Applied to drm-misc-fixes
On 8/21/26 10:46, Lizhi Hou wrote:
>
> On 8/17/26 17:00, Taimuraz Kaitmazov wrote:
>> A chain whose command_count is zero passes the payload length check,
>> because struct_size(payload, data, 0) is just the header. The fill loop
>> then does not run, so offset stays zero and the request is submitted
>> with
>> a zero-length buffer.
>>
>> On firmware without AIE2_NPU_COMMAND that ends at the opcode check,
>> since
>> op is still ERT_INVALID_CMD and aie2_get_chain_msg_op() answers
>> MSG_OP_MAX_OPCODE. aie2_get_npu_chain_msg_op() answers
>> MSG_OP_CHAIN_EXEC_NPU whatever it is given, so there the submission
>> continues to drm_clflush_virt_range(cmd_buf, 0), which reads the byte
>> before the buffer and faults on the vmap guard page. EXEC_CMD is
>> reachable by any process that can open the render node.
>>
>> Reject the request instead.
>>
>> Signed-off-by: Taimuraz Kaitmazov <taimuraz@kaitmazov.com>
>> ---
>> drm_clflush_virt_range() faulting on an empty range is a core
>> problem, and a
>> patch for it is on the list separately. This rejects the request in
>> the driver
>> regardless, since a chain carrying no commands is not something to
>> submit.
>>
>> drivers/accel/amdxdna/aie2_message.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/accel/amdxdna/aie2_message.c
>> b/drivers/accel/amdxdna/aie2_message.c
>> index dfe0fbdf066d..b4c49259a1a2 100644
>> --- a/drivers/accel/amdxdna/aie2_message.c
>> +++ b/drivers/accel/amdxdna/aie2_message.c
>> @@ -994,7 +994,7 @@ int aie2_cmdlist_multi_execbuf(struct
>> amdxdna_hwctx *hwctx,
>> }
>> ccnt = payload->command_count;
>> - if (payload_len < struct_size(payload, data, ccnt)) {
>> + if (!ccnt || payload_len < struct_size(payload, data, ccnt)) {
>
> Reviewed-by: Lizhi Hou <lizhi.hou@amd.com>
>
> I will add a Fixes tag when I merge it.
>
> Thanks,
>
> Lizhi
>
>> XDNA_DBG(xdna, "Invalid command count %d", ccnt);
>> return -EINVAL;
>> }
prev parent reply other threads:[~2026-08-24 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260818000019.369366-1-taimuraz@kaitmazov.com>
2026-08-21 17:46 ` Lizhi Hou
2026-08-24 16:40 ` Lizhi Hou [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=c66806ab-9944-0524-c36a-688dc0f05641@amd.com \
--to=lizhi.hou@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mamin506@gmail.com \
--cc=ogabbay@kernel.org \
--cc=taimuraz@kaitmazov.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®