[PATCH] dma-buf: Use fence_get_rcu_safe() for retrieving the exclusive fence

On Mon, Nov 14, 2016 at 04:37:09PM +0100, Christian König wrote: > Am 14.11.2016 um 12:55 schrieb Chris Wilson: > > The current code is subject to a race where we may try to acquire a > > reference on a stale fence: > > > > [13703.335118] WARNING: CPU: 1 PID: 14975 at ./include/linux/kref.h:46

[PATCH] dma-buf: Use fence_get_rcu_safe() for retrieving the exclusive fence

Am 14.11.2016 um 12:55 schrieb Chris Wilson: > The current code is subject to a race where we may try to acquire a > reference on a stale fence: > > [13703.335118] WARNING: CPU: 1 PID: 14975 at ./include/linux/kref.h:46 > i915_gem_object_wait+0x1a3/0x1c0 > [13703.335184] Modules linked in: >

[PATCH] dma-buf: Use fence_get_rcu_safe() for retrieving the exclusive fence

On Mon, Nov 14, 2016 at 11:55:40AM +, Chris Wilson wrote: > The current code is subject to a race where we may try to acquire a > reference on a stale fence: >From i915.ko pov, this Fixes: d07f0e59b2c7 ("drm/i915: Move GEM activity tracking into a common struct reservation_object") -Chris

[PATCH] dma-buf: Use fence_get_rcu_safe() for retrieving the exclusive fence

The current code is subject to a race where we may try to acquire a reference on a stale fence: [13703.335118] WARNING: CPU: 1 PID: 14975 at ./include/linux/kref.h:46 i915_gem_object_wait+0x1a3/0x1c0 [13703.335184] Modules linked in: [13703.335202] CPU: 1 PID: 14975 Comm: gem_concurrent_ Not