mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philipp Stanner <phasta@mailbox.org>
To: "Tvrtko Ursulin" <tursulin@ursulin.net>,
	phasta@kernel.org, 김종혁 <malhyuk97@gmail.com>,
	matthew.brost@intel.com, dakr@kernel.org
Cc: christian.koenig@amd.com, ckoenig.leichtzumerken@gmail.com,
	 dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] drm/sched: cache the timeline name to fix a use-after-free
Date: Wed, 02 Sep 2026 13:39:49 +0200	[thread overview]
Message-ID: <95e34a8771fe827e134970a3580ceeb5f661a40d.camel@mailbox.org> (raw)
In-Reply-To: <619669b6-69ea-4aa5-b91e-b29cc788e335@ursulin.net>

On Wed, 2026-09-02 at 11:20 +0100, Tvrtko Ursulin wrote:
> 
> To collate two replies in one:
> 
> On 02/09/2026 11:07, Philipp Stanner wrote:
> 
> > 
> > The issue here IMO is that we are discussing working around an issue
> > that actually stems from dma_fence not being consistently synchronized,
> > notably because of the ops->release callback being implemented.
> > 
> > ops->release is de facto deprecated, precisely for reasons like these.
> > 
> > If we could get rid of it for sched_fence, dma_fence would take care of
> > the decoupling of the name callbacks.
> > 
> > So that appears worth investigating from my POV.
> 
> I completely agree here but I am just not sure how feasible that would 
> be. We may accept to live with the cross-documentation workaround at 
> least as a start since even if feasible it could be a lot of work to 
> change sched_fence like that.


It should be enough to remove ops->release for the finished_fence for
now, since that's the one typically (always?) shared with userspace.

All that release cb does is drop yet another reference.

I think it's worth an investigation. Maybe 김종혁 can give it a look?


P.

  reply	other threads:[~2026-09-02 11:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28 14:57 [PATCH v1 0/2] drm/sched: fix a use-after-free in get_timeline_name() Jonghyuk Kim(MalHyuk)
2026-08-28 14:57 ` [PATCH v1 1/2] drm/sched: cache the timeline name to fix a use-after-free Jonghyuk Kim(MalHyuk)
2026-09-02  9:46   ` Tvrtko Ursulin
     [not found]     ` <CADQRuqtjBu7wR4kKVDcS42KLKQTr+7SBtRn24mgZ+ApettMr1A@mail.gmail.com>
2026-09-02 10:07       ` Philipp Stanner
2026-09-02 10:20         ` Tvrtko Ursulin
2026-09-02 11:39           ` Philipp Stanner [this message]
2026-09-02 13:38             ` Christian König
2026-08-28 14:57 ` [PATCH v1 2/2] drm/sched/tests: add a UAF regression test for get_timeline_name() Jonghyuk Kim(MalHyuk)
2026-09-02 10:04   ` Tvrtko Ursulin

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=95e34a8771fe827e134970a3580ceeb5f661a40d.camel@mailbox.org \
    --to=phasta@mailbox.org \
    --cc=christian.koenig@amd.com \
    --cc=ckoenig.leichtzumerken@gmail.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=malhyuk97@gmail.com \
    --cc=matthew.brost@intel.com \
    --cc=phasta@kernel.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®