renegade-project/linux-next
2
0
Fork 0
mirror of https://github.com/edk2-porting/linux-next.git synced 2024-12-15 16:53:54 +08:00
Code

dma-buf: clarify locking documentation for reservation_object_get_excl

Browse Source 
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
This commit is contained in:
Lucas Stach 2018-01-11 17:48:29 +01:00
parent 547c7138bc
commit 372c9329e5
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
include/linux/reservation.h
View File

@ -228,7 +228,8 @@ reservation_object_unlock(struct reservation_object *obj)
* @obj: the reservation object * @obj: the reservation object
* *
* Returns the exclusive fence (if any). Does NOT take a * 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 * RETURNS
* The exclusive fence or NULL * The exclusive fence or NULL