From: "Christian König" <deathsimple@vodafone.de>
To: chris@chris-wilson.co.uk, daniel.vetter@ffwll.ch,
sumit.semwal@linaro.org, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org
Subject: [PATCH] dma-fence: fix dma_fence_get_rcu_safe
Date: Mon, 4 Sep 2017 15:27:33 +0200 [thread overview]
Message-ID: <1504531653-13779-1-git-send-email-deathsimple@vodafone.de> (raw)
From: Christian König <christian.koenig@amd.com>
The logic is buggy and unnecessary complex. When dma_fence_get_rcu() fails to
acquire a reference it doesn't necessary mean that there is no fence at all.
It usually mean that the fence was replaced by a new one and in this situation
we certainly want to have the new one as result and *NOT* NULL.
Signed-off-by: Christian König <christian.koenig@amd.com>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Sumit Semwal <sumit.semwal@linaro.org>
Cc: linux-media@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org
Cc: linaro-mm-sig@lists.linaro.org
---
include/linux/dma-fence.h | 23 ++---------------------
1 file changed, 2 insertions(+), 21 deletions(-)
diff --git a/include/linux/dma-fence.h b/include/linux/dma-fence.h
index a5195a7..37f3d67 100644
--- a/include/linux/dma-fence.h
+++ b/include/linux/dma-fence.h
@@ -246,27 +246,8 @@ dma_fence_get_rcu_safe(struct dma_fence * __rcu *fencep)
struct dma_fence *fence;
fence = rcu_dereference(*fencep);
- if (!fence || !dma_fence_get_rcu(fence))
- return NULL;
-
- /* The atomic_inc_not_zero() inside dma_fence_get_rcu()
- * provides a full memory barrier upon success (such as now).
- * This is paired with the write barrier from assigning
- * to the __rcu protected fence pointer so that if that
- * pointer still matches the current fence, we know we
- * have successfully acquire a reference to it. If it no
- * longer matches, we are holding a reference to some other
- * reallocated pointer. This is possible if the allocator
- * is using a freelist like SLAB_TYPESAFE_BY_RCU where the
- * fence remains valid for the RCU grace period, but it
- * may be reallocated. When using such allocators, we are
- * responsible for ensuring the reference we get is to
- * the right fence, as below.
- */
- if (fence == rcu_access_pointer(*fencep))
- return rcu_pointer_handoff(fence);
-
- dma_fence_put(fence);
+ if (!fence || dma_fence_get_rcu(fence))
+ return fence;
} while (1);
}
--
2.7.4
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-09-04 13:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 13:27 Christian König [this message]
2017-09-04 13:40 ` [PATCH] dma-fence: fix dma_fence_get_rcu_safe Chris Wilson
2017-09-11 8:50 ` Christian König
2017-09-11 8:59 ` Chris Wilson
2017-09-11 9:06 ` Christian König
2017-09-11 9:23 ` Chris Wilson
2017-09-11 9:57 ` Christian König
2017-09-11 10:01 ` Chris Wilson
2017-09-11 11:06 ` Christian König
2017-09-20 18:20 ` Daniel Vetter
2017-09-21 7:00 ` Christian König
2017-09-21 7:29 ` Maarten Lankhorst
2017-09-29 12:34 ` Joonas Lahtinen
[not found] <1504530994-2464-1-git-send-email-deathsimple@vodafone.de>
2017-09-04 15:50 ` Christian König
-- strict thread matches above, loose matches on Subject: below --
2017-09-04 13:20 Christian König
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1504531653-13779-1-git-send-email-deathsimple@vodafone.de \
--to=deathsimple@vodafone.de \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-media@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox