From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: accel/amdxdna: Fix out-of-bounds memset in command slot handling
Date: Wed, 18 Feb 2026 06:45:36 +1000 [thread overview]
Message-ID: <review-overall-20260217185415.1781908-1-lizhi.hou@amd.com> (raw)
In-Reply-To: <20260217185415.1781908-1-lizhi.hou@amd.com>
Overall Series Review
Subject: accel/amdxdna: Fix out-of-bounds memset in command slot handling
Author: Lizhi Hou <lizhi.hou@amd.com>
Patches: 2
Reviewed: 2026-02-18T06:45:36.268063
---
This is a single-patch fix for the `accel/amdxdna` driver that addresses an out-of-bounds memset in four command slot filling functions. The bug was introduced by commit 3d32eb7a5ecf which moved the `memset()` call to occur before validation of available slot space. The fix is straightforward: move each `memset()` call to after the size checks that verify the slot buffer is large enough.
The bug is real and reachable. In the chain execution path (`aie2_cmdlist_chain_exec`), the remaining buffer size (`cmdbuf_abo->mem.size - offset`) shrinks with each iteration as slots are packed sequentially. If the remaining space is smaller than `sizeof(struct cmd_chain_slot_npu)`, the old code would `memset()` past the buffer boundary before the `*size < sizeof(*npu_slot) + ...` check could return `-EINVAL`. The fix is correct and minimal.
No cross-patch concerns since this is a single patch.
---
Generated by Claude Code Patch Reviewer
prev parent reply other threads:[~2026-02-17 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 18:54 [PATCH V1] accel/amdxdna: Fix out-of-bounds memset in command slot handling Lizhi Hou
2026-02-17 18:55 ` Mario Limonciello
2026-02-17 20:45 ` Claude review: " Claude Code Review Bot
2026-02-17 20:45 ` Claude Code Review 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=review-overall-20260217185415.1781908-1-lizhi.hou@amd.com \
--to=claude-review@example.com \
--cc=dri-devel-reviews@example.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