On 06/03/2015 12:16 PM, Zeng Linggang wrote:
> After research, We think sem_close() is thread-safe. But, there
> is not marking of sem_close() in glibc document.
Thanks, Zeng Linggang. Applied.
Cheers,
Michael
> Signed-off-by: Zeng Linggang <zenglg.jy@xxxxxxxxxxxxxx>
> ---
> man3/sem_close.3 | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/man3/sem_close.3 b/man3/sem_close.3
> index 0cc4199..5e26560 100644
> --- a/man3/sem_close.3
> +++ b/man3/sem_close.3
> @@ -51,6 +51,19 @@ set to indicate the error.
> .B EINVAL
> .I sem
> is not a valid semaphore.
> +.SH ATTRIBUTES
> +For an explanation of the terms used in this section, see
> +.BR attributes (7).
> +.TS
> +allbox;
> +lb lb lb
> +l l l.
> +Interface Attribute Value
> +T{
> +.BR sem_close ()
> +T} Thread safety MT-Safe
> +.TE
> +
> .SH CONFORMING TO
> POSIX.1-2001.
> .SH NOTES
>
--
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
