Re: Next round: revised futex(2) man page for review
From: Michael Kerrisk (man-pages) <hidden>
Date: 2015-07-27 14:44:23
Also in:
linux-api, lkml
Possibly related (same subject, not in this thread)
- 2015-10-08 · Re: Next round: revised futex(2) man page for review · Darren Hart <dvhart@infradead.org>
- 2015-10-08 · Re: Next round: revised futex(2) man page for review · Darren Hart <dvhart@infradead.org>
- 2015-10-07 · Re: Next round: revised futex(2) man page for review · Michael Kerrisk (man-pages) <hidden>
- 2015-10-07 · Re: Next round: revised futex(2) man page for review · Michael Kerrisk (man-pages) <hidden>
- 2015-08-26 · Re: Next round: revised futex(2) man page for review · Darren Hart <dvhart@infradead.org>
On 07/27/2015 04:17 PM, Heinrich Schuchardt wrote:
instruction. A thread maybe unable to << missing word acquire a lock because it is already acquired by another thread. It then may pass the lock's flag as futex word and the value representing the acquired state as the expected value to a futex() wait operation.
Thanks, Heinrich. Fixed. Cheers, Michael