[PATCH 2/2] dma-buf: fix reservation_object_wait_timeout_rcu to wait correctly v2

[Chris Wilson]

Quoting Alex Deucher (2017-08-10 18:01:49)
> From: Christian König <christian.koenig at amd.com>
> 
> With hardware resets in mind it is possible that all shared fences are
> signaled, but the exlusive isn't. Fix waiting for everything in this situation.

I'm still puzzling over this one.

Setting an exclusive fence will clear all shared, so we must have added
the shared fences after the exclusive fence. But those shared fences must
follow the exclusive fence, you should not be able to reorder the shared
fences ahead of the exclusive. If you have completed shared fences, but
incomplete exclusive, doesn't that imply you have an ordering issue?
-Chris