Browse Source

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 <gustavo.padovan@collabora.co.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Gustavo Padovan 9 years ago
parent
commit
a4ebee657c
1 changed files with 1 additions and 1 deletions
  1. 1 1
      drivers/staging/android/sw_sync.c

+ 1 - 1
drivers/staging/android/sw_sync.c

@@ -176,7 +176,7 @@ static void timeline_fence_release(struct fence *fence)
 
 
 	spin_lock_irqsave(fence->lock, flags);
 	spin_lock_irqsave(fence->lock, flags);
 	list_del(&pt->child_list);
 	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);
 		list_del(&pt->active_list);
 	spin_unlock_irqrestore(fence->lock, flags);
 	spin_unlock_irqrestore(fence->lock, flags);