Chris Wilson b016cd6ed4 dma-buf: Restore seqlock around dma_resv updates ... This reverts 67c97fb79a ("dma-buf: add reservation_object_fences helper") dd7a7d1ff2 ("drm/i915: use new reservation_object_fences helper") 0e1d8083bd ("dma-buf: further relax reservation_object_add_shared_fence") 5d344f58da ("dma-buf: nuke reservation_object seq number") The scenario that defeats simply grabbing a set of shared/exclusive fences and using them blissfully under RCU is that any of those fences may be reallocated by a SLAB_TYPESAFE_BY_RCU fence slab cache. In this scenario, while keeping the rcu_read_lock we need to establish that no fence was changed in the dma_resv after a read (or full) memory barrier. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Chris Wilson <chris@chris-wilson.co.uk> Cc: Daniel Vetter <daniel.vetter@ffwll.ch> Acked-by: Christian König <christian.koenig@amd.com> Link: https://patchwork.freedesktop.org/patch/msgid/20190814182401.25009-1-chris@chris-wilson.co.uk		2019-08-16 12:40:58 +01:00
..
dma-buf.c	dma-buf: Restore seqlock around dma_resv updates	2019-08-16 12:40:58 +01:00
dma-fence-array.c	dma-fence: Propagate errors to dma-fence-array container	2019-08-12 08:25:52 +01:00
dma-fence-chain.c	dma-buf: fix stack corruption in dma_fence_chain_release	2019-08-05 17:32:33 +02:00
dma-fence.c	dma-buf: rename reservation_object to dma_resv	2019-08-13 09:09:30 +02:00
dma-resv.c	dma-buf: Restore seqlock around dma_resv updates	2019-08-16 12:40:58 +01:00
Kconfig
Makefile	dma-buf: rename reservation_object to dma_resv	2019-08-13 09:09:30 +02:00
seqno-fence.c
sw_sync.c	dma-buf/sw_sync: Synchronize signal vs syncpt free	2019-08-13 07:57:51 +01:00
sync_debug.c
sync_debug.h
sync_file.c	dma-fence: Report the composite sync_file status	2019-08-12 10:37:52 +01:00
sync_trace.h
udmabuf.c