From: Gustavo Padovan Date: Thu, 11 Aug 2016 15:26:40 +0000 (-0300) Subject: staging/android: do not let userspace trigger WARN_ON X-Git-Tag: v4.14-rc1~2366^2~1231 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=a4ebee657c9be3afd35530cd4478b0fa514706d7;p=platform%2Fkernel%2Flinux-rpi.git staging/android: do not let userspace trigger WARN_ON Closing the timeline without waiting all fences to signal is not a critical failure, it is just bad usage from userspace so avoid calling WARN_ON in this case. Signed-off-by: Gustavo Padovan Signed-off-by: Greg Kroah-Hartman --- diff --git a/drivers/staging/android/sw_sync.c b/drivers/staging/android/sw_sync.c index 115c917..bda1f6a 100644 --- a/drivers/staging/android/sw_sync.c +++ b/drivers/staging/android/sw_sync.c @@ -176,7 +176,7 @@ static void timeline_fence_release(struct fence *fence) spin_lock_irqsave(fence->lock, flags); list_del(&pt->child_list); - if (WARN_ON_ONCE(!list_empty(&pt->active_list))) + if (!list_empty(&pt->active_list)) list_del(&pt->active_list); spin_unlock_irqrestore(fence->lock, flags);