LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity
12,274 Commits 1 Branch 197 Tags 93 MiB
Commit Graph

192 Commits

Author SHA1 Message Date
Michael Kerrisk 4e89ca063c fcntl.2: srcfix: Add some FIXMEs 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2015-01-19 10:35:32 +01:00
Michael Kerrisk 69d33b44c4 fcntl.2: Reorder text describing sealing 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2015-01-19 10:35:32 +01:00
Michael Kerrisk 9f97f3fa1c fcntl.2: Add statement about F_ADD_SEALS and F_GET_SEALS under CONFORMING TO 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2015-01-19 10:35:32 +01:00
Michael Kerrisk 4d04b15efd fcntl.2: Add EINVAL error F_ADD_SEALS 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2015-01-19 10:35:32 +01:00
Michael Kerrisk aee553ccd9 fcntl.2: Reformat EINVAL error text 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2015-01-19 10:35:32 +01:00
Michael Kerrisk 6bdad35b13 fcntl.2: Various edits; add some FIXMEs 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2015-01-19 10:35:32 +01:00
Michael Kerrisk d8943ac8c5 fcntl.2: tfix 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2015-01-19 10:35:32 +01:00
Michael Kerrisk 12cfd6227c fcntl.2: srcfix: start new sentences on new lines; rewrap source lines 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2015-01-19 10:35:32 +01:00
David Herrmann a25d701d19 fcntl.2: Document F_ADD_SEALS and F_GET_SEALS commands 
Signed-off-by: David Herrmann <dh.herrmann@gmail.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2015-01-19 10:35:32 +01:00
Michael Kerrisk 7ef5b2cd0a fcntl.2: Add reference to RLIMIT_NOFILE for F_DUPFD EINVAL error on 'arg'. 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2015-01-13 10:17:50 +01:00
David Prévot b7a3dc84e7 fcntl.2: tfix 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-09-15 11:10:26 +02:00
Michael Kerrisk 62c76ace78 memusage.1, memusagestat.1, connect.2, fcntl.2, poll.2, errno.3, rtnetlink.3, inotify.7: tstamp 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-09-07 05:03:19 -07:00
Michael Kerrisk 9bcc9e428c fcntl.2: srcfix 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-08-21 13:48:32 -05:00
Michael Kerrisk 37c240d14c fcntl.2: One must define _GNU_SOURCE to get the F_OFD_* definitions 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-08-21 13:47:25 -05:00
Michael Kerrisk c77eace5b1 iconv.1, ldd.1, connect.2, dup.2, epoll_ctl.2, eventfd.2, fallocate.2, fcntl.2, getitimer.2, inotify_add_watch.2, open.2, pipe.2, poll.2, sendmmsg.2, set_tid_address.2, shmop.2, signalfd.2, splice.2, syscalls.2, syslog.2, tee.2, vmsplice.2, ether_aton.3, mallopt.3, printf.3, profil.3, charmap.5, proc.5, epoll.7, inotify.7, libc.7, pipe.7, sched.7, socket.7, udplite.7, iconvconfig.8, ld.so.8: tstamp 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-07-08 16:14:48 +02:00
Michael Kerrisk d2b6be9a2d fcntl.2: Suggest the use of real-time signals with F_NOTIFY 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-07-08 12:22:25 +02:00
Michael Kerrisk 1ce579fc39 fcntl.2: ERRORS: Document ENOTDIR error for F_NOTIFY 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-07-08 12:07:15 +02:00
Michael Kerrisk 8be6f4e1cd fcntl.2: Use proper page cross-references in F_NOTIFY discussion 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-07-05 08:54:58 +02:00
Michael Kerrisk 5c4d5f9715 fcntl.2: The return value for F_SETPIPE_SZ is the pipe capacity 
Reported-by: Tomi Salminen <tlsalmin@gmail.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-07-01 11:40:36 +02:00
Michael Kerrisk 91085d8525 Removed trailing white space at end of lines 2014-06-14 08:03:45 +02:00
Michael Kerrisk ad5b45abe5 localedef.1, execve.2, fcntl.2, flock.2, lseek.2, open.2, open_by_handle_at.2, recvmmsg.2, sendmmsg.2, seteuid.2, setresuid.2, setreuid.2, setuid.2, statfs.2, syscalls.2, basename.3, catgets.3, getdate.3, getdirentries.3, getdtablesize.3, iconv.3, lockf.3, malloc_get_state.3, malloc_usable_size.3, matherr.3, mkdtemp.3, mkstemp.3, mq_close.3, mq_unlink.3, siginterrupt.3, system.3, locale.5, bootparam.7, environ.7, man-pages.7, signal.7, unicode.7, utf-8.7: tstamp 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-13 17:15:44 +02:00
Michael Kerrisk 864eb97814 fcntl.2: wfix 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-12 15:29:19 +02:00
Michael Kerrisk 76868835e7 fcntl.2: Add notes on F_SETLKW deadlock detection and its limitations 
Reported-by: Jeff Layton <jlayton@poochiereds.net>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:49 +02:00
Michael Kerrisk 241e02302d fcntl.2: wfix 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:49 +02:00
Michael Kerrisk d2e429c1a8 fcntl.2: The kernel does not perform deadlock detection for OFD locks 
See kernel commit 57b65325fe34ec4c917bc4e555144b4a94d9e1f7
And this mail thread:

    http://thread.gmane.org/gmane.linux.file-systems/81318/focus=81327
    From: Jeff Layton <jlayton <at> redhat.com>
    Subject: [PATCH v5 13/14] locks: skip deadlock detection on FL_FILE_PVT locks
    Date: 2014-01-09 14:19:46 GMT

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:49 +02:00
Michael Kerrisk 6451570257 fcntl.2: Under OFD locks add a reference to open(2) for explanation of OFDs 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:49 +02:00
Michael Kerrisk d068eb3b73 fcntl.2: Explain POSIX background to EACCES/EAGAIN error for F_GETLK 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk 9c26bc8c20 fcntl.2: F_OFD_GETLK fails with EAGAIN when there is a lock conflict 
For F_GETLK, POSIX allows EACCES or EAGAIN because different
implementations of traditional record locks returned one of
these errors, and portable applications had to handle either
possibility. However, that argument doesn't apply for OFD
locks, since Linux is the only implementation and it returns
EAGAIN.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk 6024e7332f fcntl.2: Describe how to check whether the kernel supports a particular command 
Reported-by: Jeff Layton <jlayton@poochiereds.net>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk 102b34d811 fcntl.2: ERRORS: add EINVAL for invalid 'cmd' 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk d9312ec7c0 fcntl.2: Minor wording improvement 
Reported-by: Jeff Layton <jlayton@poochiereds.net>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk 9044058e60 fcntl.2: Add an explicit note that mandatory locking is not in POSIX 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk f5cdb4b0fc fcntl.2: Make the warning that mandatory locks are unreliable more prominent 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk 6799ba26c9 fcntl.2: wfix 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk 9acee57885 fcntl.2: Rewrite introductory paragraphs on mandatory locking 
Make the structure more logical, and also explicitly mention
OFD locks.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk 4b5c506a2c fcntl.2: Add EINVAL error for OFD locks where 'l_pid' is not 0 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk c11b47b3b1 fcntl.2: CONFORMING TO: note that OFD locks are Linux-specific 
But they make their way into the next POSIX release

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk 97e03523e5 fcntl.2: Describe semantics for compatible and conflicting OFD locks 
And describe how threads can use OFD locks to ensure
exclusive access to a file.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk 1a93af040c fcntl.2: Detail the limitations of traditional (process-associated) locks 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk bfb147160f fcntl.2: Minor fixes to introductory par on OFD locks 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk 38702b6ccc fcntl.2: OFD locks are Linux-specific and available since Linux 3.15 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk 99b5ab7933 fcntl.2: Tweaks and rewrites of pieces of Jeff Layton's patch 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Jeff Layton 2d3e4b83a3 fcntl.2: Document open file description locks 
As provided by the fcntl() operations F_OFD_SETLK,
F_OFD_SETLKW, and F_OFD_GETLK

Signed-off-by: Jeff Layton <jlayton@poochiereds.net>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk 7562b10e23 fcntl.2: Add para introducing advisory locks and noting existence of OFD locks 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk 86fbd8d849 fcntl.2: Minor change: move some NOTES text on record locking 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk 15b4459067 fcntl.2: wfix + ffix: fine-tuning on NFSv4 client locking text 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk 70fd304581 fcntl.2: Add NOTES subhead for record locking and NFS 
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk da0d60febb fcntl.2: nfsv4leasetime controls the "contact lost" interval for NFSv4 
Jeff Layton:
   The difference here is subtle. The gracetime is how long after a reboot
   should knfsd allow clients to reclaim state (and deny the creation of
   new locks and opens). The leasetime is how long the NFSv4 lease period
   is. There is a relationship between the two that's illustrated in the
   comments above write_gracetime:

     /**
      * write_gracetime - Set or report current NFSv4 grace period time
      *
      * As above, but sets the time of the NFSv4 grace period.
      *
      * Note this should never be set to less than the *previous*
      * lease-period time, but we don't try to enforce this.  (In the common
      * case (a new boot), we don't know what the previous lease time was
      * anyway.)
      */

   The value you're interested in here is the nfsv4leasetime. If the
   client doesn't renew its lease within that period, then it's subject to
   the server giving up on it and dropping any state that it holds on that
   clients' behalf.

   Note that this is not a firm timeout. The server runs a job
   periodically to clean out expired stateful objects, and it's likely
   that there is some time (maybe even up to another whole lease period)
   between when the timeout expires and the job actually runs. If the
   client gets a RENEW in there within that window, its lease will be
   renewed and its state preserved.

Reported-by: Jeff Layton <jlayton@poochiereds.net>
Cowritten-by: Jeff Layton <jlayton@poochiereds.net>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk af8713605a fcntl.2: Refine discussion of locks when NFSv4 client loses contact with server 
Reported-by: NeilBrown <neilb@suse.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00
Michael Kerrisk 6ca357f965 fcntl.2: Note treatment of locks when an NFS client loses contact with the server 
Based on text sent by Neil Brown.

Reported-by: NeilBrown <neilb@suse.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
 2014-06-09 21:33:48 +02:00