mallinfo.3: ATTRIBUTES: Note function that is not thread-safe

The marking matches glibc marking.
The marking of functions in glibc is:
- mallinfo: MT-Unsafe init const:mallopt

Signed-off-by: Zeng Linggang <zenglg.jy@cn.fujitsu.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

diff --git a/man3/mallinfo.3 b/man3/mallinfo.3
index 7797169159d681877dc3f601e5968a07ff139126..e6661d1dd52b7d00a4db90b374b299cfce8a3623 100644 (file)
--- a/man3/mallinfo.3
+++ b/man3/mallinfo.3
@@ -107,6 +107,31 @@ This is the maximum number of bytes that could ideally
 .BR malloc_trim (3).
 .\" .SH VERSIONS
 .\" Available already in glibc 2.0, possibly earlier
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lb lb lbw28
+l l l.
+Interface      Attribute       Value
+T{
+.BR mallinfo ()
+T}     Thread safety   MT-Unsafe init const:mallopt
+.TE
+
+.BR mallinfo ()
+would access some global iternal objects. If modify them with non-atomically,
+may get inconsistent results.
+The identifier
+.I mallopt
+in
+.I const:mallopt
+mean that
+.BR mallopt ()
+would modify the global iternal objects with atomics, that make sure
+.BR mallinfo ()
+is safe enough, others modify with non-atomically maybe not.
 .SH CONFORMING TO
 This function is not specified by POSIX or the C standards.
 A similar function exists on many System V derivatives,