dma-buf: Restore seqlock around dma_resv updates

dma-buf: Restore seqlock around dma_resv updates

This reverts
1feaccdfc17a ("dma-buf: add reservation_object_fences helper")
84551ebc52f3 ("drm/i915: use new reservation_object_fences helper")
995309a0fbea ("dma-buf: further relax reservation_object_add_shared_fence")
cfbc76fc0314 ("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