mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philipp Stanner <phasta@mailbox.org>
To: "Christian König" <christian.koenig@amd.com>,
	"Felix Kuehling" <felix.kuehling@amd.com>,
	"Philipp Stanner" <phasta@kernel.org>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Sumit Semwal" <sumit.semwal@linaro.org>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	 linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] drm/amdgpu: Harden against potential deadlock
Date: Tue, 27 Oct 2026 14:18:16 +0100	[thread overview]
Message-ID: <fd9cc070b3a4e28316ad2ffce942227e33974016.camel@mailbox.org> (raw)
In-Reply-To: <1ed5c075-c66a-4144-b23b-a9d80e1fc2c1@amd.com>

On Tue, 2026-10-27 at 12:51 +0100, Christian König wrote:
> On 10/26/26 19:31, Felix Kuehling wrote:
> > We don't implement ops->signaled, and we explicitly signal the
> > fence from SW with dma_fence_signal or dma_fence_check_and_signal.
> > So the signaled flag should be the only thing that needs to be
> > checked. The flag is only set while holding the fence lock, and
> > checked while holding the fence lock. So in theory, relying on the
> > check in __dma_fence_enable_signaling should be safe.
> 
> I actually had a patch to remove that one send out month ago already,
> it was just never merged.
> 
> The call absolutely doesn't make sense since the ops->signaled
> callback isn't implemented and the bit tested before the enable
> signaling callback called.
> 
> I can take care and push the removal to amd-staging-drm-next when I
> find time.


OK, but put me on Cc please. I could need that change for my other
dma_fence-ish work. I would post the removal as a v2, too, if I don't
hear from you mid-term

Greetings,
Philipp

      reply	other threads:[~2026-10-27 13:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26 14:15 Philipp Stanner
2026-10-26 18:31 ` Felix Kuehling
2026-10-27 11:51   ` Christian König
2026-10-27 13:18     ` 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=fd9cc070b3a4e28316ad2ffce942227e33974016.camel@mailbox.org \
    --to=phasta@mailbox.org \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=felix.kuehling@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=phasta@kernel.org \
    --cc=simona@ffwll.ch \
    --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

all inboxes | Powered by JetHome®