From: Lizhi Hou <lizhi.hou@amd.com>
To: Taimuraz Kaitmazov <taimuraz@kaitmazov.com>,
Min Ma <mamin506@gmail.com>, Oded Gabbay <ogabbay@kernel.org>
Cc: <dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] accel/amdxdna: put the chained BO when its mapping fails
Date: Mon, 24 Aug 2026 09:40:15 -0700 [thread overview]
Message-ID: <17811ffc-f33b-b3ac-865b-18138239e0dd@amd.com> (raw)
In-Reply-To: <d359981d-710b-dc52-9741-39cd5ed884a1@amd.com>
Applied to drm-misc-fixes
On 8/21/26 08:39, Lizhi Hou wrote:
>
> On 8/19/26 16:08, Taimuraz Kaitmazov wrote:
>> amdxdna_cmd_set_error() looks up the first BO of a command chain, which
>> takes a reference, and drops it at the end of the function. The
>> mapping of
>> that BO is established in between, and the failure path returns
>> without the
>> put, so the reference is leaked.
>>
>> Ordinary use does not reach it. The chain has been submitted before
>> any of
>> this runs, so aie2_cmdlist_fill_slot() has already called
>> amdxdna_cmd_get_op() on that BO and amdxdna_gem_vmap() has cached its
>> address. What makes it reachable is that the BO is resolved again by
>> handle here, and the handle is userspace's to recycle: closing it after
>> submission and importing a dma-buf whose exporter implements no vmap
>> onto
>> the same id leaves amdxdna_gem_get_obj() returning an object this cannot
>> map, since prime_import() types every import AMDXDNA_BO_SHARE.
>>
>> Signed-off-by: Taimuraz Kaitmazov <taimuraz@kaitmazov.com>
>> ---
>> drivers/accel/amdxdna/amdxdna_ctx.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/accel/amdxdna/amdxdna_ctx.c
>> b/drivers/accel/amdxdna/amdxdna_ctx.c
>> index 855da8c79a1c..4e4a9cf5c327 100644
>> --- a/drivers/accel/amdxdna/amdxdna_ctx.c
>> +++ b/drivers/accel/amdxdna/amdxdna_ctx.c
>> @@ -183,8 +183,10 @@ int amdxdna_cmd_set_error(struct amdxdna_gem_obj
>> *abo,
>> if (!abo)
>> return -EINVAL;
>> cmd = amdxdna_gem_vmap(abo);
>> - if (!cmd)
>> + if (!cmd) {
>> + amdxdna_gem_put_obj(abo);
>> return -ENOMEM;
>> + }
>
> Thanks for the fix. I will add 'Fixes' tag when I merge.
>
> Reviewed-by: Lizhi Hou <lizhi.hou@amd.com>
>
>
> Lizhi
>
>> }
>> memset(cmd->data, 0xff, abo->mem.size - sizeof(*cmd));
prev parent reply other threads:[~2026-08-24 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260819230852.287751-1-taimuraz@kaitmazov.com>
2026-08-21 15:39 ` 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=17811ffc-f33b-b3ac-865b-18138239e0dd@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®