mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philipp Stanner <phasta@mailbox.org>
To: "Baineng Shou" <shoubaineng@gmail.com>,
	"Sumit Semwal" <sumit.semwal@linaro.org>,
	"Christian König" <christian.koenig@amd.com>,
	"André Draszik" <andre.draszik@linaro.org>
Cc: Tvrtko Ursulin <tursulin@ursulin.net>,
	Philipp Stanner <phasta@kernel.org>,
	 Akash Goel <akash.goel@arm.com>,
	linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
	 linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
	 stable@vger.kernel.org
Subject: Re: [PATCH] dma-fence: Fix dma_fence_timeline_name() to call get_timeline_name()
Date: Thu, 25 Jun 2026 17:01:15 +0200	[thread overview]
Message-ID: <de3b9b978ffeeb43c18d877080e93823214313ec.camel@mailbox.org> (raw)
In-Reply-To: <20260625141227.38931-1-shoubaineng@gmail.com>

+Cc André

On Thu, 2026-06-25 at 22:12 +0800, Baineng Shou wrote:
> dma_fence_timeline_name() incorrectly invokes ops->get_driver_name()
> instead of ops->get_timeline_name(), so every caller receives the
> driver name where the timeline name was expected.
> 
> This is a copy-paste regression that has resurfaced twice. It was
> originally introduced by commit 62918542b7bf ("dma-fence: Fix sparse
> warnings due __rcu annotations") when adding the __rcu casts, fixed
> by commit 033559473dd3 ("dma-fence: Fix safe access wrapper to call
> timeline name method"), and then accidentally reintroduced by commit
> e58b4dea9054 ("dma-buf/dma-fence: Add dma_fence_test_signaled_flag()")
> when both wrappers were refactored to use the new helper.
> 
> Signed-off-by: Baineng Shou <shoubaineng@gmail.com>

André has caught this a few days ago already:

https://lore.kernel.org/dri-devel/20260618-linux-drm_crtc_fix-v1-1-801f29c9853d@linaro.org/


To save my honor I want to state that e58b4dea9054 did not actually *do
this* change. But merging it must have caused it somehow, since that
commit was still based on the old bug. I guess somewhere in conflict
resolution somehow tho old code must have entered.


P.

> ---
>  drivers/dma-buf/dma-fence.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/dma-buf/dma-fence.c b/drivers/dma-buf/dma-fence.c
> index b3bfa6943a8e..5292d714419b 100644
> --- a/drivers/dma-buf/dma-fence.c
> +++ b/drivers/dma-buf/dma-fence.c
> @@ -1202,7 +1202,7 @@ const char __rcu *dma_fence_timeline_name(struct dma_fence *fence)
>  	/* RCU protection is required for safe access to returned string */
>  	ops = rcu_dereference(fence->ops);
>  	if (!dma_fence_test_signaled_flag(fence))
> -		return (const char __rcu *)ops->get_driver_name(fence);
> +		return (const char __rcu *)ops->get_timeline_name(fence);
>  	else
>  		return (const char __rcu *)"signaled-timeline";
>  }
		

      reply	other threads:[~2026-06-25 15:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-25 14:12 Baineng Shou
2026-06-25 15:01 ` Philipp Stanner [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=de3b9b978ffeeb43c18d877080e93823214313ec.camel@mailbox.org \
    --to=phasta@mailbox.org \
    --cc=akash.goel@arm.com \
    --cc=andre.draszik@linaro.org \
    --cc=christian.koenig@amd.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=phasta@kernel.org \
    --cc=shoubaineng@gmail.com \
    --cc=stable@vger.kernel.org \
    --cc=sumit.semwal@linaro.org \
    --cc=tursulin@ursulin.net \
    /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®