posix_fallocate.3: Clarify text relating to MT-safety

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2015-10-05 09:59:24 +01:00
parent 141c1d0547
commit 624fbe44d9
1 changed files with 3 additions and 3 deletions

View File

@ -111,7 +111,7 @@ l l l.
Interface Attribute Value
T{
.BR posix_fallocate ()
T} Thread safety MT-Safe
T} Thread safety MT-Safe (but see NOTES)
.TE
.SH CONFORMING TO
POSIX.1-2001.
@ -143,7 +143,7 @@ In the glibc implementation,
.BR posix_fallocate ()
is implemented using the
.BR fallocate (2)
system call.
system call, which is MT-safe.
If the underlying filesystem does not support
.BR fallocate (2),
then the operation is emulated with the following caveats:
@ -169,7 +169,7 @@ flags, the function will fail with the error
In general, the emulation is not MT-safe.
On Linux, applications may use
.BR fallocate (2)
if they cannot work around the emulation caveats.
if they cannot tolerate the emulation caveats.
In general, this is
only recommended if the application plans to terminate the operation if
.B EOPNOTSUPP