LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

futex.2: Fix discussion of FUTEX_LOCK_PI 'timeout' argument 

Reading futex_lock_pi(), it appears that the timeout is *not*
interpreted in the same way as for FUTEX_WAKE.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2015-01-14 13:47:33 +01:00
parent a8b5b324e3
commit 9ce19cf1b7
1 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
man2/futex.2
View File

@ -649,11 +649,18 @@ The owner inherits either the priority or the bandwidth of the waiter.
This inheritance follows the lock chain in the case of
nested locking and performs deadlock detection.
.\" FIXME tglx says "The timeout argument is handled as described in
.\" FUTEX_WAIT." However, it appears to me that this is not right.
.\" Is the following formulation correct.
The
.I timeout
.\" FIXME Is this true??????????????????????
argument is handled as described in
.BR FUTEX_WAIT .
argument provides a timeout for the lock attempt.
It is interpreted as an absolute time, measured against the
.BR CLOCK_REALTIME
clock.
If
.I timeout
is NULL, the operation will block indefinitely.
The
.IR uaddr2 ,