summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorLucas Stach <l.stach@pengutronix.de>2018-01-11 17:48:29 +0100
committerLucas Stach <l.stach@pengutronix.de>2019-02-27 23:51:51 +0100
commit372c9329e5aa896683999301d9cb10ef14da92af (patch)
tree92dde1f746abe9e1234a64512ba1cf23bbb9e0c0 /include
parent547c7138bcfb869c4cda6548f358eaa64102cccf (diff)
dma-buf: clarify locking documentation for reservation_object_get_excl
The documentation was misleading, as for a lot of use-cases holding the RCU read side lock is sufficient. Signed-off-by: Lucas Stach <l.stach@pengutronix.de> Reviewed-by: Christian König <christian.koenig@amd.com> Link: https://patchwork.freedesktop.org/patch/msgid/20180111165302.25556-2-l.stach@pengutronix.de
Diffstat (limited to 'include')
-rw-r--r--include/linux/reservation.h3
1 files changed, 2 insertions, 1 deletions
diff --git a/include/linux/reservation.h b/include/linux/reservation.h
index 2f0ffca35780..ee750765cc94 100644
--- a/include/linux/reservation.h
+++ b/include/linux/reservation.h
@@ -228,7 +228,8 @@ reservation_object_unlock(struct reservation_object *obj)
* @obj: the reservation object
*
* Returns the exclusive fence (if any). Does NOT take a
- * reference. The obj->lock must be held.
+ * reference. Writers must hold obj->lock, readers may only
+ * hold a RCU read side lock.
*
* RETURNS
* The exclusive fence or NULL