dma-buf: nuke reservation_object seq number
authorChristian König <christian.koenig@amd.com>
Mon, 5 Aug 2019 12:24:55 +0000 (14:24 +0200)
committerChristian König <christian.koenig@amd.com>
Tue, 13 Aug 2019 07:07:58 +0000 (09:07 +0200)
commit5d344f58da760b226562e7d5199fb73294eb93fa
treedabe9434fb720c4c0d80b7078cccf3acde6e0f9a
parentd3c6dd1fb30d3853c2012549affe75c930f4a2f9
dma-buf: nuke reservation_object seq number

The only remaining use for this is to protect against setting a new exclusive
fence while we grab both exclusive and shared. That can also be archived by
looking if the exclusive fence has changed or not after completing the
operation.

v2: switch setting excl fence to rcu_assign_pointer

Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Link: https://patchwork.freedesktop.org/patch/322380/
drivers/dma-buf/reservation.c
include/linux/reservation.h