diff options
author | 2016-08-11 12:26:40 -0300 | |
---|---|---|
committer | 2016-08-15 16:39:45 +0200 | |
commit | a4ebee657c9be3afd35530cd4478b0fa514706d7 (patch) | |
tree | f3a1e7961a8270fa3d71c9947152821e8f72a4a7 | |
parent | staging: android: ion: Get rid of ion_reserve (diff) | |
download | linux-dev-a4ebee657c9be3afd35530cd4478b0fa514706d7.tar.xz linux-dev-a4ebee657c9be3afd35530cd4478b0fa514706d7.zip |
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>
-rw-r--r-- | drivers/staging/android/sw_sync.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/staging/android/sw_sync.c b/drivers/staging/android/sw_sync.c index 115c9174705f..bda1f6a220c1 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); |