drm/i915: Check for allocation failure
authorColin Ian King <colin.king@canonical.com>
Fri, 19 May 2017 17:56:17 +0000 (18:56 +0100)
committerChris Wilson <chris@chris-wilson.co.uk>
Fri, 19 May 2017 19:36:32 +0000 (20:36 +0100)
The memory allocation for C is not being null checked and hence we
could end up with a null pointer dereference. Fix this with a null
pointer check. (I really should have noticed this when I was fixing an
earlier issue.)

Detected by CoverityScan, CID#1436406 ("Dereference null return")

Fixes: 47624cc3301b60 ("drm/i915: Import the kfence selftests for i915_sw_fence")
Signed-off-by: Colin Ian King <colin.king@canonical.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20170519175617.7036-1-colin.king@canonical.com
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
drivers/gpu/drm/i915/selftests/i915_sw_fence.c

index c31d439fae3a174f09af813fd7a7657035013ac4..19d145d6bf523873b79ac5325985d4371ee43d46 100644 (file)
@@ -123,6 +123,11 @@ static int test_dag(void *arg)
        }
 
        C = alloc_fence();
+       if (!C) {
+               ret = -ENOMEM;
+               goto err_B;
+       }
+
        if (i915_sw_fence_await_sw_fence_gfp(B, C, GFP_KERNEL) == -EINVAL) {
                pr_err("invalid cycle detected\n");
                goto err_C;