following commit was removed FUTEX_FD implementation. commit 82af7aca56c67061420d618cc5a30f0fd4106b80 Author: Eric Sesterhenn <snakebyte@gmx.de> Date: Fri Jan 25 10:40:46 2008 +0100 Removal of FUTEX_FD Since FUTEX_FD was scheduled for removal in June 2007 lets remove it. Google Code search found no users for it and NGPT was abandoned in 2003 according to IBM. futex.h is left untouched to make sure the id does not get reassigned. Since queue_me() has no users left it is commented out to avoid a warning, i didnt remove it completely since it is part of the internal api (matching unqueue_me()) Signed-off-by: Eric Sesterhenn <snakebyte@gmx.de> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (removed rest) Acked-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> but the man page of futex (http://www.kernel.org/doc/man-pages/online/pages/man2/futex.2.html) still have following explanation. It should be removed too, I think. FUTEX_FD (present up to and including Linux 2.6.25) To support asynchronous wakeups, this operation associates a file descriptor with a futex. If another process executes a FUTEX_WAKE, the process will receive the signal number that was passed in val. The calling process must close the returned file descriptor after use. The arguments timeout, uaddr2 and val3 are ignored. To prevent race conditions, the caller should test if the futex has been upped after FUTEX_FD returns. Because it was inherently racy, FUTEX_FD has been removed from Linux 2.6.26 onwards.
Hi Motohiro, The man page clearly states that FUTEX_FD is removed, but the text needs to stay there, so that people using older kernels know about FUTEX_FD. So, I don't plan to make any change to the page. Cheers, Michael
ok. I'll close this ticket. Thanks.
Reply-To: mtk.manpages@googlemail.com > ok. I'll close this ticket. Thanks!