nouveau: fix client work fence deletion race
authorDave Airlie <airlied@redhat.com>
Thu, 15 Jun 2023 02:22:11 +0000 (12:22 +1000)
committerDave Airlie <airlied@redhat.com>
Fri, 16 Jun 2023 01:19:34 +0000 (11:19 +1000)
commitc8a5d5ea3ba6a18958f8d76430e4cd68eea33943
tree7b5c23ef341126939e9fe01b8ac3067e13d5200d
parentc8ac109e21e12a25dd127a426c813d771ff90b1e
nouveau: fix client work fence deletion race

This seems to have existed for ever but is now more apparant after
commit 9bff18d13473 ("drm/ttm: use per BO cleanup workers")

My analysis: two threads are running, one in the irq signalling the
fence, in dma_fence_signal_timestamp_locked, it has done the
DMA_FENCE_FLAG_SIGNALLED_BIT setting, but hasn't yet reached the
callbacks.

The second thread in nouveau_cli_work_ready, where it sees the fence is
signalled, so then puts the fence, cleanups the object and frees the
work item, which contains the callback.

Thread one goes again and tries to call the callback and causes the
use-after-free.

Proposed fix: lock the fence signalled check in nouveau_cli_work_ready,
so either the callbacks are done or the memory is freed.

Reviewed-by: Karol Herbst <kherbst@redhat.com>
Fixes: 11e451e74050 ("drm/nouveau: remove fence wait code from deferred client work handler")
Cc: stable@vger.kernel.org
Signed-off-by: Dave Airlie <airlied@redhat.com>
Link: https://lore.kernel.org/dri-devel/20230615024008.1600281-1-airlied@gmail.com/
drivers/gpu/drm/nouveau/nouveau_drm.c