From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Li Ming <ming.li@zohomail.com>,
Sumit Semwal <sumit.semwal@linaro.org>,
Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Cc: "Christian König" <ckoenig.leichtzumerken@gmail.com>,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dma-fence: Dereference correct dma_fence in dma_fence_chain_find_seqno()
Date: Mon, 30 Mar 2026 11:52:38 +0200 [thread overview]
Message-ID: <45754304-12c4-44b2-965c-fee97f839808@gmail.com> (raw)
In-Reply-To: <20260327-fix_dma_fence_chain_find_seqno-v1-1-60e80bfb43c8@zohomail.com>
On 3/27/26 15:33, Li Ming wrote:
> dma_fence_chain_find_seqno() uses dma_fence_chain_for_each() to walk a
> given dma_fence_chain. dma_fence_chain_for_each() always holds a
> reference for the current fence during iteration. The reference must
> be dropped after breaking out. Instead of dereferencing the last fence
> as intended, dma_fence_chain_find_seqno() incorrectly dereferences the
> first fence in the chain.
Well once more: Absolutely clear NAK and please search the mailing list for similar changes before you send a patch out.
The existing code is perfectly correct and I can't count how often I had to reject that patch.
I think the functionality is obvious but it looks like we really need to add a comment here.
Regards,
Christian.
>
> Fixes: 7bf60c52e093 ("dma-buf: add new dma_fence_chain container v7")
> Signed-off-by: Li Ming <ming.li@zohomail.com>
> ---
> drivers/dma-buf/dma-fence-chain.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dma-buf/dma-fence-chain.c b/drivers/dma-buf/dma-fence-chain.c
> index a8a90acf4f34..71fa173aef13 100644
> --- a/drivers/dma-buf/dma-fence-chain.c
> +++ b/drivers/dma-buf/dma-fence-chain.c
> @@ -103,7 +103,7 @@ int dma_fence_chain_find_seqno(struct dma_fence **pfence, uint64_t seqno)
> to_dma_fence_chain(*pfence)->prev_seqno < seqno)
> break;
> }
> - dma_fence_put(&chain->base);
> + dma_fence_put(*pfence);
>
> return 0;
> }
>
> ---
> base-commit: c369299895a591d96745d6492d4888259b004a9e
> change-id: 20260327-fix_dma_fence_chain_find_seqno-7adea64efe01
>
> Best regards,
> --
> Li Ming <ming.li@zohomail.com>
>
prev parent reply other threads:[~2026-03-30 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 14:33 [PATCH] dma-fence: Dereference correct dma_fence in dma_fence_chain_find_seqno() Li Ming
2026-03-30 9:52 ` Christian König [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=45754304-12c4-44b2-965c-fee97f839808@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lionel.g.landwerlin@intel.com \
--cc=ming.li@zohomail.com \
--cc=sumit.semwal@linaro.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