OSDN Git Service
(root)
/
tomoyo
/
tomoyo-test1.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
| inline |
side by side
(parent:
547c713
)
dma-buf: clarify locking documentation for reservation_object_get_excl
author
Lucas Stach
<l.stach@pengutronix.de>
Thu, 11 Jan 2018 16:48:29 +0000
(17:48 +0100)
committer
Lucas Stach
<l.stach@pengutronix.de>
Wed, 27 Feb 2019 22:51:51 +0000
(23:51 +0100)
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
include/linux/reservation.h
patch
|
blob
|
history
diff --git
a/include/linux/reservation.h
b/include/linux/reservation.h
index
2f0ffca
..
ee75076
100644
(file)
--- 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