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 v2] accel/amdxdna: fix NULL deref and GEM object leak in error paths
Date: Mon, 31 Aug 2026 13:38:03 -0700 [thread overview]
Message-ID: <44919809-5a71-70b9-84dc-1c4cac3eac46@amd.com> (raw)
In-Reply-To: <20260829085644.38103-1-denizaydogan1902@gmail.com>
On 8/29/26 01:56, Deniz Aydogan wrote:
> amdxdna_cmd_submit() does not set job->cmd_bo for internal driver
> commands that pass AMDXDNA_INVALID_BO_HANDLE. When such a job hits
> an error or completes normally, both the submit error path and
> amdxdna_sched_job_cleanup() call amdxdna_gem_put_obj(job->cmd_bo)
> unconditionally, dereferencing NULL.
>
> Separately, amdxdna_cmd_set_error() acquires a GEM reference via
> amdxdna_gem_get_obj() when handling a chained command, but leaks it
> when the subsequent amdxdna_gem_vmap() returns NULL.
>
> Guard all three amdxdna_gem_put_obj(job->cmd_bo) call sites with a
> NULL check and release the GEM reference on vmap failure.
>
> Fixes: 3ba13f5e7180 ("Merge tag 'devicetree-fixes-for-7.3-1'")
> Signed-off-by: Deniz Aydogan <denizaydogan1902@gmail.com>
> ---
> drivers/accel/amdxdna/amdxdna_ctx.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/accel/amdxdna/amdxdna_ctx.c b/drivers/accel/amdxdna/amdxdna_ctx.c
> index 31a414c3f..a806702ec 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;
This is fixed by:
https://lore.kernel.org/all/17811ffc-f33b-b3ac-865b-18138239e0dd@amd.com/
> + }
> }
>
> memset(cmd->data, 0xff, abo->mem.size - sizeof(*cmd));
> @@ -575,7 +577,8 @@ void amdxdna_sched_job_cleanup(struct amdxdna_sched_job *job)
> trace_amdxdna_debug_point(job->hwctx->name, job->seq, "job release");
> amdxdna_pm_suspend_put(job->hwctx->client->xdna);
> amdxdna_arg_bos_put(job);
> - amdxdna_gem_put_obj(job->cmd_bo);
> + if (job->cmd_bo)
> + amdxdna_gem_put_obj(job->cmd_bo);
The current code will not crash because drm_gem_object_put will check
the if the obj pointer is NULL.
And I agree it is more robuster to check job->cmd_bo. Could you remove
the "Fixes" tag and previous leak fix?
Thanks
Lizhi
> dma_fence_put(job->fence);
> mmdrop(job->mm);
> }
> @@ -676,7 +679,8 @@ int amdxdna_cmd_submit(struct amdxdna_client *client,
> put_bos:
> amdxdna_arg_bos_put(job);
> cmd_put:
> - amdxdna_gem_put_obj(job->cmd_bo);
> + if (job->cmd_bo)
> + amdxdna_gem_put_obj(job->cmd_bo);
> free_job:
> if (job->mm)
> mmdrop(job->mm);
next prev parent reply other threads:[~2026-08-31 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 8:00 [PATCH] accel/amdxdna: fix NULL deref and GEM object leak in error paths Deniz Aydogan
2026-08-29 8:56 ` [PATCH v2] " Deniz Aydogan
2026-08-31 20:38 ` Lizhi Hou [this message]
2026-09-02 11:49 ` [PATCH v2] accel/amdxdna: add NULL check for job->cmd_bo Deniz Aydogan
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=44919809-5a71-70b9-84dc-1c4cac3eac46@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