fcntl.2: Reword discussion of mandatory lock bug a litte

Jeff Layton confirmed that the bug remains even in modern kernels.

Reviewed-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

diff --git a/man2/fcntl.2 b/man2/fcntl.2
index 5eb310c0d52b589460fc14c4c50364159d16fdab..b57aa2a6d8d5a83bc98b69abdeb216f7d452f1a8 100644 (file)
--- a/man2/fcntl.2
+++ b/man2/fcntl.2
@@ -1325,10 +1325,16 @@ has permission to send signals to.
 Despite this error return, the file descriptor owner is set,
 and signals will be sent to the owner.
 .SS Mandatory locking
-The implementation of mandatory locking in all known versions of Linux
+The Linux implementation of mandatory locking
 is subject to race conditions which render it unreliable:
 .\" http://marc.info/?l=linux-kernel&m=119013491707153&w=2
-a
+.\"
+.\" Reconfirmed by Jeff Layton
+.\"     From: Jeff Layton <jlayton <at> redhat.com>
+.\"     Subject: Re: Status of fcntl() mandatory locking
+.\"     Newsgroups: gmane.linux.file-systems
+.\"     Date: 2014-04-28 10:07:57 GMT
+.\"     http://thread.gmane.org/gmane.linux.file-systems/84481/focus=84518
 .BR write (2)
 call that overlaps with a lock may modify data after the mandatory lock is
 acquired;