]> git.ipfire.org Git - thirdparty/kernel/stable.git/commitdiff
dma-buf/sw_sync: Avoid recursive lock during fence signal
authorRob Clark <robdclark@chromium.org>
Fri, 18 Aug 2023 14:59:38 +0000 (07:59 -0700)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 30 Aug 2023 14:35:16 +0000 (16:35 +0200)
[ Upstream commit e531fdb5cd5ee2564b7fe10c8a9219e2b2fac61e ]

If a signal callback releases the sw_sync fence, that will trigger a
deadlock as the timeline_fence_release recurses onto the fence->lock
(used both for signaling and the the timeline tree).

To avoid that, temporarily hold an extra reference to the signalled
fences until after we drop the lock.

(This is an alternative implementation of https://patchwork.kernel.org/patch/11664717/
which avoids some potential UAF issues with the original patch.)

v2: Remove now obsolete comment, use list_move_tail() and
    list_del_init()

Reported-by: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
Fixes: d3c6dd1fb30d ("dma-buf/sw_sync: Synchronize signal vs syncpt free")
Signed-off-by: Rob Clark <robdclark@chromium.org>
Link: https://patchwork.freedesktop.org/patch/msgid/20230818145939.39697-1-robdclark@gmail.com
Reviewed-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Christian König <christian.koenig@amd.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
drivers/dma-buf/sw_sync.c

index 114b36674af4246233e9cb7295504cf52fe9b007..29a4e2bb61f03e4558ee0e5481d3bf0a35a1b736 100644 (file)
@@ -201,6 +201,7 @@ static const struct dma_fence_ops timeline_fence_ops = {
  */
 static void sync_timeline_signal(struct sync_timeline *obj, unsigned int inc)
 {
+       LIST_HEAD(signalled);
        struct sync_pt *pt, *next;
 
        trace_sync_timeline(obj);
@@ -213,21 +214,20 @@ static void sync_timeline_signal(struct sync_timeline *obj, unsigned int inc)
                if (!timeline_fence_signaled(&pt->base))
                        break;
 
-               list_del_init(&pt->link);
+               dma_fence_get(&pt->base);
+
+               list_move_tail(&pt->link, &signalled);
                rb_erase(&pt->node, &obj->pt_tree);
 
-               /*
-                * A signal callback may release the last reference to this
-                * fence, causing it to be freed. That operation has to be
-                * last to avoid a use after free inside this loop, and must
-                * be after we remove the fence from the timeline in order to
-                * prevent deadlocking on timeline->lock inside
-                * timeline_fence_release().
-                */
                dma_fence_signal_locked(&pt->base);
        }
 
        spin_unlock_irq(&obj->lock);
+
+       list_for_each_entry_safe(pt, next, &signalled, link) {
+               list_del_init(&pt->link);
+               dma_fence_put(&pt->base);
+       }
 }
 
 /**