[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1Wcyo3-0000Eg-UC@fencepost.gnu.org>
Date: Wed, 23 Apr 2014 11:09:51 -0400
From: ams@....org (Alfred M. Szmidt)
To: Jeff Layton <jlayton@...hat.com>
CC: libc-alpha@...rceware.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, tytso@....edu, dalias@...c.org,
mtk.manpages@...il.com, samba-technical@...ts.samba.org,
nfs-ganesha-devel@...ts.sourceforge.net, carlos@...hat.com,
metze@...ba.org, hch@...radead.org, bharrosh@...asas.com
Subject: Re: [RFC][glibc PATCH] fcntl-linux.h: add new definitions and manual updates for open file description locks
@@ -2890,7 +2894,7 @@ Get flags associated with the open file. @xref{File Status Flags}.
Set flags associated with the open file. @xref{File Status Flags}.
@item F_GETLK
-Get a file lock. @xref{File Locks}.
+Test a file lock. @xref{File Locks}.
F_GETLK does get the (first) lock which blocks; it doesn't test for
it. "Retrieves information about the first blocking lock ..." or
something might be better than the original
@@ -2898,6 +2902,18 @@ Set or clear a file lock. @xref{File Locks}.
@item F_SETLKW
Like @code{F_SETLK}, but wait for completion. @xref{File Locks}.
+@...m F_OFD_GETLK
+Test a open file description lock. @xref{Open File Description Locks}.
+Specific to Linux.
Likewise. You infact write that it does get the lock information
later in the document wrt. F_OFD_GETLK.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists