[PATCH] stdio_ext.3: ATTRIBUTES: Note functions that are not thread-safe

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The functions __fbufsize(), __fpending(), __fpurge() and
__fsetlocking() are not thread safe.

Signed-off-by: Peng Haitao <penght@xxxxxxxxxxxxxx>
---
 man3/stdio_ext.3 | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/man3/stdio_ext.3 b/man3/stdio_ext.3
index fb5767a..d2578fe 100644
--- a/man3/stdio_ext.3
+++ b/man3/stdio_ext.3
@@ -129,6 +129,25 @@ output to a terminal is forced out, say before reading keyboard input.)
 The
 .BR __fpurge ()
 function discards the contents of the stream's buffer.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+The
+.BR __fbufsize (),
+.BR __fpending (),
+.BR __fpurge ()
+and
+.BR __fsetlocking ()
+functions do not lock the stream, so they are not thread-safe.
+.LP
+The
+.BR __flbf (),
+.BR __freadable (),
+.BR __freading (),
+.BR __fwritable (),
+.BR __fwriting ()
+and
+.BR _flushlbf ()
+functions are thread-safe.
 .SH SEE ALSO
 .BR flockfile (3),
 .BR fpurge (3)
-- 
1.8.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux