Calling the signaling a NULL fence is obviously a coding error in a
driver. Those functions unfortunately just returned silently without
raising a warning.

Signed-off-by: Christian König <christian.koe...@amd.com>
---
 drivers/dma-buf/dma-fence.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/dma-buf/dma-fence.c b/drivers/dma-buf/dma-fence.c
index 0393a9bba3a8..325a263ac798 100644
--- a/drivers/dma-buf/dma-fence.c
+++ b/drivers/dma-buf/dma-fence.c
@@ -412,7 +412,7 @@ int dma_fence_signal_timestamp(struct dma_fence *fence, 
ktime_t timestamp)
        unsigned long flags;
        int ret;
 
-       if (!fence)
+       if (WARN_ON(!fence))
                return -EINVAL;
 
        spin_lock_irqsave(fence->lock, flags);
@@ -464,7 +464,7 @@ int dma_fence_signal(struct dma_fence *fence)
        int ret;
        bool tmp;
 
-       if (!fence)
+       if (WARN_ON(!fence))
                return -EINVAL;
 
        tmp = dma_fence_begin_signalling();
-- 
2.34.1

Reply via email to