[PATCH] dma-buf/sw_sync: fix lockdep anger

2016-10-16 Thread Rob Clark
On Thu, Oct 13, 2016 at 4:17 PM, Chris Wilson wrote: > On Thu, Oct 13, 2016 at 04:04:05PM -0400, Rob Clark wrote: >> We were holding the wrong lock to be using fence_is_signaled_locked(). >> And holding the child_list_lock over something that could end up calling >> fence cb's angers lockdep: >>

[PATCH] dma-buf/sw_sync: fix lockdep anger

2016-10-13 Thread Chris Wilson
On Thu, Oct 13, 2016 at 04:04:05PM -0400, Rob Clark wrote: > We were holding the wrong lock to be using fence_is_signaled_locked(). > And holding the child_list_lock over something that could end up calling > fence cb's angers lockdep: > > == > [

[PATCH] dma-buf/sw_sync: fix lockdep anger

2016-10-13 Thread Rob Clark
On Thu, Oct 13, 2016 at 4:17 PM, Chris Wilson wrote: > On Thu, Oct 13, 2016 at 04:04:05PM -0400, Rob Clark wrote: >> We were holding the wrong lock to be using fence_is_signaled_locked(). >> And holding the child_list_lock over something that could end up calling >> fence cb's angers lockdep: >>

[PATCH] dma-buf/sw_sync: fix lockdep anger

2016-10-13 Thread Rob Clark
We were holding the wrong lock to be using fence_is_signaled_locked(). And holding the child_list_lock over something that could end up calling fence cb's angers lockdep: == [ INFO: possible circular locking dependency detected ] 4.7.0-rc7+ #489