Commit 3ea411c5 authored by Maarten Lankhorst's avatar Maarten Lankhorst Committed by Greg Kroah-Hartman

android: fix reference leak in sync_fence_create

According to the documentation sync_fence_create takes ownership of the point,
not a reference on the point.

This fixes a memory leak introduced in 3.17's android fence rework.
Signed-off-by: default avatarMaarten Lankhorst <maarten.lankhorst@canonical.com>
Cc: Colin Cross <ccross@google.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent d9fdb9fb
...@@ -199,7 +199,6 @@ struct sync_fence *sync_fence_create(const char *name, struct sync_pt *pt) ...@@ -199,7 +199,6 @@ struct sync_fence *sync_fence_create(const char *name, struct sync_pt *pt)
fence->num_fences = 1; fence->num_fences = 1;
atomic_set(&fence->status, 1); atomic_set(&fence->status, 1);
fence_get(&pt->base);
fence->cbs[0].sync_pt = &pt->base; fence->cbs[0].sync_pt = &pt->base;
fence->cbs[0].fence = fence; fence->cbs[0].fence = fence;
if (fence_add_callback(&pt->base, &fence->cbs[0].cb, if (fence_add_callback(&pt->base, &fence->cbs[0].cb,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment