From: sashiko-bot@kernel.org
To: tongzhiwei <tongzhiwei@cmss.chinamobile.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/syncobj: Fix fence and syncobj leak on dma_fence_chain_alloc failure
Date: Fri, 06 Nov 2026 10:10:02 +0000 [thread overview]
Message-ID: <sashiko-outbox-201188@kernel.org> (raw)
In-Reply-To: <20261106095730.166-1-tongzhiwei@cmss.chinamobile.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] drm/syncobj: missing Fixes trailer for
drm_syncobj_import_sync_file_fence()
--
commit de478817c7c05dbb269859f891ebb406ae0d952f
Author: tongzhiwei <tongzhiwei@cmss.chinamobile.com>
> drm/syncobj: Fix fence and syncobj leak on dma_fence_chain_alloc failure
>
> NOTE: this commit is worked by llm completely
>
> In drm_syncobj_import_sync_file_fence(), when point is non-zero and
> dma_fence_chain_alloc() returns NULL, the function returns -ENOMEM
> without releasing the fence reference (obtained via sync_file_get_fence)
> or the syncobj reference (obtained via drm_syncobj_find). Both
> references are permanently leaked.
>
> Add dma_fence_put(fence) and drm_syncobj_put(syncobj) before returning
> -ENOMEM on the allocation failure path.
>
> Assisted-by: LLM
> Signed-off-by: tongzhiwei <tongzhiwei@cmss.chinamobile.com>
[Severity: Low]
This fixes a reference leak introduced with timeline sync_file import
support. Should the commit message include a Fixes tag:
Fixes: c2d3a7300695 ("drm/syncobj: Extend EXPORT_SYNC_FILE for timeline syncobjs")
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261106095730.166-1-tongzhiwei@cmss.chinamobile.com?part=1
prev parent reply other threads:[~2026-11-06 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 9:57 [PATCH] drm/syncobj: Fix fence and syncobj leak on dma_fence_chain_alloc failure tongzhiwei
2026-11-06 10:10 ` sashiko-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=sashiko-outbox-201188@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tongzhiwei@cmss.chinamobile.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.