From: Philipp Stanner <phasta@mailbox.org>
To: Edward Adam Davis <eadavis@sina.com>, sashiko-bot@kernel.org
Cc: media-ci@linuxtv.org, sashiko-reviews@lists.linux.dev,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, syzkaller-bugs@googlegroups.com,
sumit.semwal@linaro.org, christian.koenig@amd.com,
phasta@kernel.org, robin.clark@oss.qualcomm.com
Subject: Re: [PATCH v2] dma-buf/sw_sync: Optimize the retrieval of fence reference counts
Date: Thu, 05 Nov 2026 08:49:49 +0100 [thread overview]
Message-ID: <75367a9a19c1e9a007422e0a1b8ed0acaca2492a.camel@mailbox.org> (raw)
In-Reply-To: <20261105052707.55911-1-eadavis@sina.com>
On Thu, 2026-11-05 at 13:27 +0800, Edward Adam Davis wrote:
> ---
> v1 -> v2: use dma_fence_get_rcu() and remove link & erase pt node
Ideally, one avoids sending new versions within 24 hours :)
>
> drivers/dma-buf/sw_sync.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/dma-buf/sw_sync.c b/drivers/dma-buf/sw_sync.c
> index 8df20b0218a9..261bc98b1ed6 100644
> --- a/drivers/dma-buf/sw_sync.c
> +++ b/drivers/dma-buf/sw_sync.c
> @@ -221,7 +221,11 @@ static void sync_timeline_signal(struct sync_timeline *obj, unsigned int inc)
> if (!timeline_fence_signaled(&pt->base))
> break;
>
> - dma_fence_get(&pt->base);
> + if (!dma_fence_get_rcu(&pt->base)) {
You must hold the rcu_read_lock() while doing that, don't you?
This probably works "by coincidence" since the surrounding spinlock
also disables preemption, like the rcu lock does.
That spinlock, why can't it guard the dma_fence reference? Doesn't obj-
>pt_list hold its own reference?
P.
next prev parent reply other threads:[~2026-11-05 7:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sashiko-outbox-198550@kernel.org>
2026-11-05 5:27 ` Edward Adam Davis
2026-11-05 7:49 ` Philipp Stanner [this message]
2026-11-05 9:35 ` Edward Adam Davis
2026-11-05 11:21 ` Philipp Stanner
2026-11-05 10:03 ` Christian König
2026-11-05 12:37 ` Edward Adam Davis
2026-11-05 13:55 ` Danilo Krummrich
2026-11-05 14:14 ` Christian König
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=75367a9a19c1e9a007422e0a1b8ed0acaca2492a.camel@mailbox.org \
--to=phasta@mailbox.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eadavis@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=media-ci@linuxtv.org \
--cc=phasta@kernel.org \
--cc=robin.clark@oss.qualcomm.com \
--cc=sashiko-bot@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sumit.semwal@linaro.org \
--cc=syzkaller-bugs@googlegroups.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®