[PATCH] dl_iterate_phdr.3: ATTRIBUTES: Note function that is thread-safe

[PATCH] dl_iterate_phdr.3: ATTRIBUTES: Note function that is thread-safe

[Zeng Linggang]

After research, We think dl_iterate_phdr() is thread-safe. But, there
is not marking of dl_iterate_phdr() in glibc document.

Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
 man3/dl_iterate_phdr.3 | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/man3/dl_iterate_phdr.3 b/man3/dl_iterate_phdr.3
index be06d1f..d83ca35 100644
--- a/man3/dl_iterate_phdr.3
+++ b/man3/dl_iterate_phdr.3
@@ -154,6 +154,19 @@ function returns whatever value was returned by the last call to
 .SH VERSIONS
 .BR dl_iterate_phdr ()
 has been supported in glibc since version 2.2.4.
+.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 dl_iterate_phdr ()
+T}	Thread safety	MT-Safe
+.TE
+
 .SH CONFORMING TO
 The
 .BR dl_iterate_phdr ()
-- 
1.9.3

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

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

[Zeng Linggang]

After research, We think getaddrinfo(), freeaddrinfo() and
gai_strerror() are thread-safe. But, there are not markings
of them in glibc document.

Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
 man3/getaddrinfo.3 | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/man3/getaddrinfo.3 b/man3/getaddrinfo.3
index 4e8a55b..b2004fe 100644
--- a/man3/getaddrinfo.3
+++ b/man3/getaddrinfo.3
@@ -592,6 +592,23 @@ function translates these error codes to a human readable string,
 suitable for error reporting.
 .SH FILES
 .I /etc/gai.conf
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw15 lb lb
+l l l.
+Interface	Attribute	Value
+T{
+.BR getaddrinfo ()
+T}	Thread safety	MT-Safe env locale
+T{
+.BR freeaddrinfo (),
+.BR gai_strerror ()
+T}	Thread safety	MT-Safe
+.TE
+
 .SH CONFORMING TO
 POSIX.1-2001.
 The
-- 
1.9.3

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

Re: [PATCH] getaddrinfo.3: ATTRIBUTES: Note functions that are thread-safe

[Michael Kerrisk (man-pages)]

On 06/03/2015 12:16 PM, Zeng Linggang wrote:
> After research, We think getaddrinfo(), freeaddrinfo() and
> gai_strerror() are 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-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
>  man3/getaddrinfo.3 | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
> 
> diff --git a/man3/getaddrinfo.3 b/man3/getaddrinfo.3
> index 4e8a55b..b2004fe 100644
> --- a/man3/getaddrinfo.3
> +++ b/man3/getaddrinfo.3
> @@ -592,6 +592,23 @@ function translates these error codes to a human readable string,
>  suitable for error reporting.
>  .SH FILES
>  .I /etc/gai.conf
> +.SH ATTRIBUTES
> +For an explanation of the terms used in this section, see
> +.BR attributes (7).
> +.TS
> +allbox;
> +lbw15 lb lb
> +l l l.
> +Interface	Attribute	Value
> +T{
> +.BR getaddrinfo ()
> +T}	Thread safety	MT-Safe env locale
> +T{
> +.BR freeaddrinfo (),
> +.BR gai_strerror ()
> +T}	Thread safety	MT-Safe
> +.TE
> +
>  .SH CONFORMING TO
>  POSIX.1-2001.
>  The
> 


-- 
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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH] getnameinfo.3: ATTRIBUTES: Note function that is thread-safe

[Zeng Linggang]

After research, We think getnameinfo() is thread-safe. But, there
is not marking of getnameinfo() in glibc document.

Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
 man3/getnameinfo.3 | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/man3/getnameinfo.3 b/man3/getnameinfo.3
index 3d4c042..45a62a1 100644
--- a/man3/getnameinfo.3
+++ b/man3/getnameinfo.3
@@ -203,6 +203,19 @@ suitable for error reporting.
 .SH VERSIONS
 .BR getnameinfo ()
 is provided in glibc since version 2.1.
+.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 getnameinfo ()
+T}	Thread safety	MT-Safe env locale
+.TE
+
 .SH CONFORMING TO
 RFC\ 2553, POSIX.1-2001.
 .SH NOTES
-- 
1.9.3

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

Re: [PATCH] getnameinfo.3: ATTRIBUTES: Note function that is thread-safe

[Michael Kerrisk (man-pages)]

On 06/03/2015 12:16 PM, Zeng Linggang wrote:
> After research, We think getnameinfo() is thread-safe. But, there
> is not marking of getnameinfo() in glibc document.

Thanks, Zeng Linggang. Applied.

Cheers,

Michael


> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
>  man3/getnameinfo.3 | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/man3/getnameinfo.3 b/man3/getnameinfo.3
> index 3d4c042..45a62a1 100644
> --- a/man3/getnameinfo.3
> +++ b/man3/getnameinfo.3
> @@ -203,6 +203,19 @@ suitable for error reporting.
>  .SH VERSIONS
>  .BR getnameinfo ()
>  is provided in glibc since version 2.1.
> +.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 getnameinfo ()
> +T}	Thread safety	MT-Safe env locale
> +.TE
> +
>  .SH CONFORMING TO
>  RFC\ 2553, 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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH] getprotoent.3: ATTRIBUTES: Note functions that aren't thread-safe

[Zeng Linggang]

The marking matches glibc marking.
markings of functions in glibc are:
- getprotoent:      MT-Unsafe race:protoent race:protoentbuf locale

- getprotobyname:   MT-Unsafe race:protobyname locale

- getprotobynumber: MT-Unsafe race:protobynumber locale

- setprotoent:      MT-Unsafe race:protoent locale
- endprotoent:      MT-Unsafe race:protoent locale

Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
 man3/getprotoent.3 | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 51 insertions(+)

diff --git a/man3/getprotoent.3 b/man3/getprotoent.3
index d41e926..56fac15 100644
--- a/man3/getprotoent.3
+++ b/man3/getprotoent.3
@@ -137,6 +137,57 @@ error occurs or the end of the file is reached.
 .I /etc/protocols
 protocol database file
 .PD
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw18 lb lbw28
+l l l.
+Interface	Attribute	Value
+T{
+.BR getprotoent ()
+T}	Thread safety	T{
+MT-Unsafe race:protoent
+.br
+race:protoentbuf locale
+T}
+T{
+.BR getprotobyname ()
+T}	Thread safety	T{
+MT-Unsafe race:protobyname
+.br
+locale
+T}
+T{
+.BR getprotobynumber ()
+T}	Thread safety	T{
+MT-Unsafe race:protobynumber
+.br
+locale
+T}
+T{
+.BR setprotoent (),
+.br
+.BR endprotoent ()
+T}	Thread safety	T{
+MT-Unsafe race:protoent
+.br
+locale
+T}
+.TE
+
+In the above table,
+.I protoent
+in
+.I race:protoent
+signifies that if any of the functions
+.BR setprotoent (3),
+.BR getprotoent (3),
+or
+.BR endprotoent (3)
+are used in parallel in different threads of a program,
+then data races could occur.
 .SH CONFORMING TO
 4.3BSD, POSIX.1-2001.
 .SH SEE ALSO
-- 
1.9.3

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

Re: [PATCH] getprotoent.3: ATTRIBUTES: Note functions that aren't thread-safe

[Michael Kerrisk (man-pages)]

On 06/03/2015 12:16 PM, Zeng Linggang wrote:
> The marking matches glibc marking.
> markings of functions in glibc are:
> - getprotoent:      MT-Unsafe race:protoent race:protoentbuf locale
> 
> - getprotobyname:   MT-Unsafe race:protobyname locale
> 
> - getprotobynumber: MT-Unsafe race:protobynumber locale
> 
> - setprotoent:      MT-Unsafe race:protoent locale
> - endprotoent:      MT-Unsafe race:protoent locale

Thanks, Zeng Linggang. Applied.

Cheers,

Michael


> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
>  man3/getprotoent.3 | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 51 insertions(+)
> 
> diff --git a/man3/getprotoent.3 b/man3/getprotoent.3
> index d41e926..56fac15 100644
> --- a/man3/getprotoent.3
> +++ b/man3/getprotoent.3
> @@ -137,6 +137,57 @@ error occurs or the end of the file is reached.
>  .I /etc/protocols
>  protocol database file
>  .PD
> +.SH ATTRIBUTES
> +For an explanation of the terms used in this section, see
> +.BR attributes (7).
> +.TS
> +allbox;
> +lbw18 lb lbw28
> +l l l.
> +Interface	Attribute	Value
> +T{
> +.BR getprotoent ()
> +T}	Thread safety	T{
> +MT-Unsafe race:protoent
> +.br
> +race:protoentbuf locale
> +T}
> +T{
> +.BR getprotobyname ()
> +T}	Thread safety	T{
> +MT-Unsafe race:protobyname
> +.br
> +locale
> +T}
> +T{
> +.BR getprotobynumber ()
> +T}	Thread safety	T{
> +MT-Unsafe race:protobynumber
> +.br
> +locale
> +T}
> +T{
> +.BR setprotoent (),
> +.br
> +.BR endprotoent ()
> +T}	Thread safety	T{
> +MT-Unsafe race:protoent
> +.br
> +locale
> +T}
> +.TE
> +
> +In the above table,
> +.I protoent
> +in
> +.I race:protoent
> +signifies that if any of the functions
> +.BR setprotoent (3),
> +.BR getprotoent (3),
> +or
> +.BR endprotoent (3)
> +are used in parallel in different threads of a program,
> +then data races could occur.
>  .SH CONFORMING TO
>  4.3BSD, POSIX.1-2001.
>  .SH SEE ALSO
> 


-- 
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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH] getrpcport.3: ATTRIBUTES: Note function that is thread-safe

[Zeng Linggang]

After research, We think getrpcport() is thread-safe. But, there
is not marking of getrpcport() in glibc document.

Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
 man3/getrpcport.3 | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/man3/getrpcport.3 b/man3/getrpcport.3
index 13f970f..476f203 100644
--- a/man3/getrpcport.3
+++ b/man3/getrpcport.3
@@ -35,6 +35,19 @@ is registered but not with version
 it will still return a port number (for some version of the program)
 indicating that the program is indeed registered.
 The version mismatch will be detected upon the first call to the service.
+.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 getrpcport ()
+T}	Thread safety	MT-Safe env locale
+.TE
+
 .SH CONFORMING TO
 Not in POSIX.1-2001.
 Present on the BSDs, Solaris, and many other systems.
-- 
1.9.3

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

Re: [PATCH] getrpcport.3: ATTRIBUTES: Note function that is thread-safe

[Michael Kerrisk (man-pages)]

On 06/03/2015 12:16 PM, Zeng Linggang wrote:
> After research, We think getrpcport() is thread-safe. But, there
> is not marking of getrpcport() in glibc document.


Thanks, Zeng Linggang. Applied.

Cheers,

Michael


> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
>  man3/getrpcport.3 | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/man3/getrpcport.3 b/man3/getrpcport.3
> index 13f970f..476f203 100644
> --- a/man3/getrpcport.3
> +++ b/man3/getrpcport.3
> @@ -35,6 +35,19 @@ is registered but not with version
>  it will still return a port number (for some version of the program)
>  indicating that the program is indeed registered.
>  The version mismatch will be detected upon the first call to the service.
> +.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 getrpcport ()
> +T}	Thread safety	MT-Safe env locale
> +.TE
> +
>  .SH CONFORMING TO
>  Not in POSIX.1-2001.
>  Present on the BSDs, Solaris, and many other systems.
> 


-- 
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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH] getservent.3: ATTRIBUTES: Note functions that aren't thread-safe

[Zeng Linggang]

The marking matches glibc marking.
markings of functions in glibc are:
- getservent:    MT-Unsafe race:servent race:serventbuf locale

- getservbyname: MT-Unsafe race:servbyname locale

- getservbyport: MT-Unsafe race:servbyport locale

- setservent:    MT-Unsafe race:servent locale
- endservent:    MT-Unsafe race:servent locale

Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
 man3/getservent.3 | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 51 insertions(+)

diff --git a/man3/getservent.3 b/man3/getservent.3
index c229053..a475b2e 100644
--- a/man3/getservent.3
+++ b/man3/getservent.3
@@ -154,6 +154,57 @@ error occurs or the end of the file is reached.
 .TP
 .I /etc/services
 services database file
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw15 lb lbw25
+l l l.
+Interface	Attribute	Value
+T{
+.BR getservent ()
+T}	Thread safety	T{
+MT-Unsafe race:servent
+.br
+race:serventbuf locale
+T}
+T{
+.BR getservbyname ()
+T}	Thread safety	T{
+MT-Unsafe race:servbyname
+.br
+locale
+T}
+T{
+.BR getservbyport ()
+T}	Thread safety	T{
+MT-Unsafe race:servbyport
+.br
+locale
+T}
+T{
+.BR setservent (),
+.br
+.BR endservent ()
+T}	Thread safety	T{
+MT-Unsafe race:servent
+.br
+locale
+T}
+.TE
+
+In the above table,
+.I servent
+in
+.I race:servent
+signifies that if any of the functions
+.BR setservent (3),
+.BR getservent (3),
+or
+.BR endservent (3)
+are used in parallel in different threads of a program,
+then data races could occur.
 .SH CONFORMING TO
 4.3BSD, POSIX.1-2001.
 .SH SEE ALSO
-- 
1.9.3

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

Re: [PATCH] getservent.3: ATTRIBUTES: Note functions that aren't thread-safe

[Michael Kerrisk (man-pages)]

On 06/03/2015 12:16 PM, Zeng Linggang wrote:
> The marking matches glibc marking.
> markings of functions in glibc are:
> - getservent:    MT-Unsafe race:servent race:serventbuf locale
> 
> - getservbyname: MT-Unsafe race:servbyname locale
> 
> - getservbyport: MT-Unsafe race:servbyport locale
> 
> - setservent:    MT-Unsafe race:servent locale
> - endservent:    MT-Unsafe race:servent locale


Thanks, Zeng Linggang. Applied.

Cheers,

Michael


> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
>  man3/getservent.3 | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 51 insertions(+)
> 
> diff --git a/man3/getservent.3 b/man3/getservent.3
> index c229053..a475b2e 100644
> --- a/man3/getservent.3
> +++ b/man3/getservent.3
> @@ -154,6 +154,57 @@ error occurs or the end of the file is reached.
>  .TP
>  .I /etc/services
>  services database file
> +.SH ATTRIBUTES
> +For an explanation of the terms used in this section, see
> +.BR attributes (7).
> +.TS
> +allbox;
> +lbw15 lb lbw25
> +l l l.
> +Interface	Attribute	Value
> +T{
> +.BR getservent ()
> +T}	Thread safety	T{
> +MT-Unsafe race:servent
> +.br
> +race:serventbuf locale
> +T}
> +T{
> +.BR getservbyname ()
> +T}	Thread safety	T{
> +MT-Unsafe race:servbyname
> +.br
> +locale
> +T}
> +T{
> +.BR getservbyport ()
> +T}	Thread safety	T{
> +MT-Unsafe race:servbyport
> +.br
> +locale
> +T}
> +T{
> +.BR setservent (),
> +.br
> +.BR endservent ()
> +T}	Thread safety	T{
> +MT-Unsafe race:servent
> +.br
> +locale
> +T}
> +.TE
> +
> +In the above table,
> +.I servent
> +in
> +.I race:servent
> +signifies that if any of the functions
> +.BR setservent (3),
> +.BR getservent (3),
> +or
> +.BR endservent (3)
> +are used in parallel in different threads of a program,
> +then data races could occur.
>  .SH CONFORMING TO
>  4.3BSD, POSIX.1-2001.
>  .SH SEE ALSO
> 


-- 
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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

[Zeng Linggang]

After research, We think malloc_get_state() and malloc_set_state() are
thread-safe. But, there are not markings of them in glibc document.

Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
 man3/malloc_get_state.3 | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/man3/malloc_get_state.3 b/man3/malloc_get_state.3
index 6f3f87d..20dde14 100644
--- a/man3/malloc_get_state.3
+++ b/man3/malloc_get_state.3
@@ -83,6 +83,20 @@ is a more recent version than this implementation knows about,
 .\" if((ms->version & ~0xffl) > (MALLOC_STATE_VERSION & ~0xffl)) return -2;
 .BR malloc_set_state ()
 returns \-2.
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw19 lb lb
+l l l.
+Interface	Attribute	Value
+T{
+.BR malloc_get_state (),
+.BR malloc_set_state ()
+T}	Thread safety	MT-Safe
+.TE
+
 .SH CONFORMING TO
 These functions are GNU extensions.
 .SH NOTES
-- 
1.9.3

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

Re: [PATCH] malloc_get_state.3: ATTRIBUTES: Note functions that are thread-safe

[Michael Kerrisk (man-pages)]

On 06/03/2015 12:16 PM, Zeng Linggang wrote:
> After research, We think malloc_get_state() and malloc_set_state() are
> 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-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
>  man3/malloc_get_state.3 | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/man3/malloc_get_state.3 b/man3/malloc_get_state.3
> index 6f3f87d..20dde14 100644
> --- a/man3/malloc_get_state.3
> +++ b/man3/malloc_get_state.3
> @@ -83,6 +83,20 @@ is a more recent version than this implementation knows about,
>  .\" if((ms->version & ~0xffl) > (MALLOC_STATE_VERSION & ~0xffl)) return -2;
>  .BR malloc_set_state ()
>  returns \-2.
> +.SH ATTRIBUTES
> +For an explanation of the terms used in this section, see
> +.BR attributes (7).
> +.TS
> +allbox;
> +lbw19 lb lb
> +l l l.
> +Interface	Attribute	Value
> +T{
> +.BR malloc_get_state (),
> +.BR malloc_set_state ()
> +T}	Thread safety	MT-Safe
> +.TE
> +
>  .SH CONFORMING TO
>  These functions are GNU extensions.
>  .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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH] malloc_trim.3: ATTRIBUTES: Note function that is thread-safe

[Zeng Linggang]

After research, We think malloc_trim() is thread-safe. But, there
is not marking of malloc_trim() in glibc document.

Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
 man3/malloc_trim.3 | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/man3/malloc_trim.3 b/man3/malloc_trim.3
index 74ef07e..769f1c1 100644
--- a/man3/malloc_trim.3
+++ b/man3/malloc_trim.3
@@ -57,6 +57,19 @@ or 0 if it was not possible to release any memory.
 No errors are defined.
 .\" .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 lb
+l l l.
+Interface	Attribute	Value
+T{
+.BR malloc_trim ()
+T}	Thread safety	MT-Safe
+.TE
+
 .SH CONFORMING TO
 This function is a GNU extension.
 .SH NOTES
-- 
1.9.3

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

Re: [PATCH] malloc_trim.3: ATTRIBUTES: Note function that is thread-safe

[Michael Kerrisk (man-pages)]

On 06/03/2015 12:16 PM, Zeng Linggang wrote:
> After research, We think malloc_trim() is thread-safe. But, there
> is not marking of malloc_trim() in glibc document.


Thanks, Zeng Linggang. Applied.

Cheers,

Michael


> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
>  man3/malloc_trim.3 | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/man3/malloc_trim.3 b/man3/malloc_trim.3
> index 74ef07e..769f1c1 100644
> --- a/man3/malloc_trim.3
> +++ b/man3/malloc_trim.3
> @@ -57,6 +57,19 @@ or 0 if it was not possible to release any memory.
>  No errors are defined.
>  .\" .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 lb
> +l l l.
> +Interface	Attribute	Value
> +T{
> +.BR malloc_trim ()
> +T}	Thread safety	MT-Safe
> +.TE
> +
>  .SH CONFORMING TO
>  This function is a GNU extension.
>  .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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH] rpmatch.3: ATTRIBUTES: Note function that is thread-safe

[Zeng Linggang]

The marking matches glibc marking.
The marking of functions in glibc is:
- rpmatch: MT-Safe locale

Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
 man3/rpmatch.3 | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/man3/rpmatch.3 b/man3/rpmatch.3
index 702c591..0abfea6 100644
--- a/man3/rpmatch.3
+++ b/man3/rpmatch.3
@@ -96,6 +96,19 @@ or anywhere else, but indicates a
 failure of the regex engine (but this case is indistinguishable from
 that of an unrecognized value of
 .IR response ).
+.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 rpmatch ()
+T}	Thread safety	MT-Safe locale
+.TE
+
 .SH CONFORMING TO
 .BR rpmatch ()
 is not required by any standard, but
-- 
1.9.3

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

Re: [PATCH] rpmatch.3: ATTRIBUTES: Note function that is thread-safe

[Michael Kerrisk (man-pages)]

On 06/03/2015 12:16 PM, Zeng Linggang wrote:
> The marking matches glibc marking.
> The marking of functions in glibc is:
> - rpmatch: MT-Safe locale


Thanks, Zeng Linggang. Applied.

Cheers,

Michael


> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
>  man3/rpmatch.3 | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/man3/rpmatch.3 b/man3/rpmatch.3
> index 702c591..0abfea6 100644
> --- a/man3/rpmatch.3
> +++ b/man3/rpmatch.3
> @@ -96,6 +96,19 @@ or anywhere else, but indicates a
>  failure of the regex engine (but this case is indistinguishable from
>  that of an unrecognized value of
>  .IR response ).
> +.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 rpmatch ()
> +T}	Thread safety	MT-Safe locale
> +.TE
> +
>  .SH CONFORMING TO
>  .BR rpmatch ()
>  is not required by any standard, but
> 


-- 
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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH] sem_close.3: ATTRIBUTES: Note function that is thread-safe

[Zeng Linggang]

After research, We think sem_close() is thread-safe. But, there
is not marking of sem_close() in glibc document.

Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
 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
-- 
1.9.3

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

Re: [PATCH] sem_close.3: ATTRIBUTES: Note function that is thread-safe

[Michael Kerrisk (man-pages)]

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-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
>  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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] dl_iterate_phdr.3: ATTRIBUTES: Note function that is thread-safe

[Michael Kerrisk (man-pages)]

On 06/03/2015 12:16 PM, Zeng Linggang wrote:
> After research, We think dl_iterate_phdr() is thread-safe. But, there
> is not marking of dl_iterate_phdr() in glibc document.

Thanks, Zeng Linggang. Applied.

Cheers,

Michael

> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
>  man3/dl_iterate_phdr.3 | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/man3/dl_iterate_phdr.3 b/man3/dl_iterate_phdr.3
> index be06d1f..d83ca35 100644
> --- a/man3/dl_iterate_phdr.3
> +++ b/man3/dl_iterate_phdr.3
> @@ -154,6 +154,19 @@ function returns whatever value was returned by the last call to
>  .SH VERSIONS
>  .BR dl_iterate_phdr ()
>  has been supported in glibc since version 2.2.4.
> +.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 dl_iterate_phdr ()
> +T}	Thread safety	MT-Safe
> +.TE
> +
>  .SH CONFORMING TO
>  The
>  .BR dl_iterate_phdr ()
> 


-- 
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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html