On 06/11/2015 04:04 AM, Zeng Linggang wrote:
> After research, We think
> * fts_open(),
> * fts_set(),
> * fts_close(),
> are thread-safe. And
> * fts_read(),
> * fts_children(),
> are not thread-safe. But, there are not
> markings of them in glibc document.
Thanks, Zeng Linggang. Applied.
Cheers,
Michael
> Signed-off-by: Zeng Linggang <zenglg.jy@xxxxxxxxxxxxxx>
> ---
> man3/fts.3 | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/man3/fts.3 b/man3/fts.3
> index 7427fac..418a69a 100644
> --- a/man3/fts.3
> +++ b/man3/fts.3
> @@ -772,6 +772,25 @@ as follows:
> The options were invalid.
> .SH VERSIONS
> These functions are available in Linux since glibc2.
> +.SH ATTRIBUTES
> +For an explanation of the terms used in this section, see
> +.BR attributes (7).
> +.TS
> +allbox;
> +lbw34 lb lb
> +l l l.
> +Interface Attribute Value
> +T{
> +.BR fts_open (),
> +.BR fts_set (),
> +.BR fts_close ()
> +T} Thread safety MT-Safe
> +T{
> +.BR fts_read (),
> +.BR fts_children ()
> +T} Thread safety MT-Unsafe
> +.TE
> +
> .SH CONFORMING TO
> 4.4BSD.
> .SH BUGS
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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
