Qian Lei
0e7d2e7fcd
mq_close.3: ATTRIBUTES: Note function that is thread-safe
...
The function mq_close() is thread safe.
Signed-off-by: Qian Lei <qianl.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-10 16:45:44 +02:00
Qian Lei
7675964213
mq_unlink.3: ATTRIBUTES: Note function that is thread-safe
...
The function mq_unlink() is thread safe.
Signed-off-by: Qian Lei <qianl.fnst@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-10 16:45:05 +02:00
Michael Kerrisk
29d3bdc482
seteuid.2, setresuid.2, setreuid.2, setuid.2: spfix
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-09 21:41:32 +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
d20d9d33ab
open.2: Rework and extend the discussion of open file descriptions
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-09 21:33:49 +02:00
Michael Kerrisk
22603b1d5c
lseek.2: Add reference to open(2) for discussion of file descriptors and OFDs
...
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
5879ccc0d3
fork.2: Add notes on inheritance of flock() and OFD locks across fork()
...
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
Michael Kerrisk
9584daf7f3
fcntl.2: Minor rewording
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-09 21:33:48 +02:00
Michael Kerrisk
cf118c620f
fcntl.2: srcfix
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-09 21:33:47 +02:00
Michael Kerrisk
91ac17b2c7
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>
2014-06-09 21:33:47 +02:00
Michael Kerrisk
05a0fb665a
flock.2: In some modern BSDs, fcntl() and flock() locks do interact
...
So, reword and extend the discussion of this topic in NOTES.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-09 21:33:38 +02:00
Michael Kerrisk
b1b70920af
flock.2: Move NOTES text describing implementation of flock()
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-09 21:30:37 +02:00
Michael Kerrisk
e449654fdb
flock.2: Add more details on NFS, including Linux 2.6.37 changes
...
Also: move NOTES text describing interaction of fcntl()
and flock() locks.
Reviewed-by: NeilBrown <neilb@suse.de>
Reported-by: NeilBrown <neilb@suse.de>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-09 21:30:37 +02:00
Peng Haitao
fee98b6e5c
mkdtemp.3: ATTRIBUTES: Note function that is thread-safe
...
The function mkdtemp() is thread safe.
Signed-off-by: Peng Haitao <penght@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-09 21:28:42 +02:00
Peng Haitao
61d995d649
basename.3: ATTRIBUTES: Note functions that are thread-safe
...
The functions basename() and dirname() are thread safe.
Signed-off-by: Peng Haitao <penght@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-09 21:28:42 +02:00
Peng Haitao
527c8d41b9
system.3: ATTRIBUTES: Note function that is thread-safe
...
The function system() is thread safe.
Signed-off-by: Peng Haitao <penght@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-09 21:28:42 +02:00
Michael Kerrisk
f4dc1f56ee
catgets.3: wfix
...
Reported-by: Peng Haitao <penght@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-09 21:28:42 +02:00
Peng Haitao
8114fa1417
catgets.3: ATTRIBUTES: Note function that is thread-safe
...
The function catgets() is thread safe.
Signed-off-by: Peng Haitao <penght@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-09 21:28:42 +02:00
Michael Kerrisk
3f205b20d7
environ.7: SEE ALSO: add env(1), printenv(1), ld.so(8)
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-09 21:28:38 +02:00
Yuri Kozlov
f2f50fed25
fanotify_mark.2: tfix
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-08 21:16:39 +02:00
Yuri Kozlov
d1c05d0b78
send.2: tfix
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-08 21:16:06 +02:00
Michael Kerrisk
79745892b6
charsets.7: Drop unneeded text on UTF-8 for Biblical Hebrew
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-06 06:37:46 +02:00
Marko Myllynen
03ba14f978
localedef.1: Align with recent charmap(5) / repertoiremap(5) changes
...
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
2014-06-05 20:18:02 +02:00