From: Lizhi Hou <lizhi.hou@amd.com>
To: Deniz Aydogan <denizaydogan1902@gmail.com>,
<amd-gfx@lists.freedesktop.org>
Cc: <dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] accel/amdxdna: fix double-free on mailbox channel stop
Date: Mon, 31 Aug 2026 14:28:15 -0700 [thread overview]
Message-ID: <7c533a4d-233f-f884-e79b-59d47c0555da@amd.com> (raw)
In-Reply-To: <20260828212405.13124-1-denizaydogan1902@gmail.com>
On 8/28/26 14:24, Deniz Aydogan wrote:
> mailbox_release_msg() frees the message with kfree() but does not
> remove it from the xarray. The stop function uses two loops to walk
> pending entries in cyclic order, but since released entries remain in
> the xarray, overlapping ranges cause the same entry to be freed twice.
>
> In particular, when next_msgid is 0 (the initial value after kzalloc),
> xa_for_each_start() covers all entries from index 0 onward, and
> xa_for_each_range() with max=(u32)(0 - 1) = U32_MAX also covers all
> entries. Every pending message gets double-freed.
>
> Use xa_for_each() to iterate all remaining entries exactly once.
> At this point the IRQ is already freed and the workqueue is drained,
> so traversal order does not matter.
>
> Fixes: 3ba13f5e7180 ("Merge tag 'devicetree-fixes-for-7.3-1'")
> Signed-off-by: Deniz Aydogan <denizaydogan1902@gmail.com>
> ---
> drivers/accel/amdxdna/amdxdna_mailbox.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/accel/amdxdna/amdxdna_mailbox.c b/drivers/accel/amdxdna/amdxdna_mailbox.c
> index cc8865f4e..271617347 100644
> --- a/drivers/accel/amdxdna/amdxdna_mailbox.c
> +++ b/drivers/accel/amdxdna/amdxdna_mailbox.c
> @@ -556,9 +556,7 @@ void xdna_mailbox_stop_channel(struct mailbox_channel *mb_chann)
> drain_workqueue(mb_chann->work_q);
>
> /* We can clean up and release resources */
> - xa_for_each_start(&mb_chann->chan_xa, msg_id, mb_msg, mb_chann->next_msgid)
> - mailbox_release_msg(mb_chann, mb_msg);
> - xa_for_each_range(&mb_chann->chan_xa, msg_id, mb_msg, 0, mb_chann->next_msgid - 1)
> + xa_for_each(&mb_chann->chan_xa, msg_id, mb_msg)
The msg need to be released in sequence. And I would suggest to release
msgid in mailbox_release_msg()
@@ -192,6 +192,7 @@ static void mailbox_release_msg(struct
mailbox_channel *mb_chann,
mb_msg->pkg.header.id, mb_msg->pkg.header.opcode);
if (mb_msg->notify_cb)
mb_msg->notify_cb(mb_msg->handle, NULL, 0);
+ mailbox_release_msgid(mb_chann, mb_msg->pkg.header.id);
kfree(mb_msg);
Thanks,
Lizhi
> mailbox_release_msg(mb_chann, mb_msg);
> xa_destroy(&mb_chann->chan_xa);
>
prev parent reply other threads:[~2026-08-31 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 21:24 Deniz Aydogan
2026-08-31 21:28 ` 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=7c533a4d-233f-f884-e79b-59d47c0555da@amd.com \
--to=lizhi.hou@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=denizaydogan1902@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®