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

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

[Zeng Linggang]

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

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

diff --git a/man3/fexecve.3 b/man3/fexecve.3
index 77c1a98..ddfc07f 100644
--- a/man3/fexecve.3
+++ b/man3/fexecve.3
@@ -91,6 +91,19 @@ filesystem could not be accessed.
 .SH VERSIONS
 .BR fexecve ()
 is implemented since glibc 2.3.2.
+.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 fexecve ()
+T}	Thread safety	MT-Safe
+.TE
+
 .SH CONFORMING TO
 POSIX.1-2008.
 This function is not specified in POSIX.1-2001,
-- 
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] getnetent_r.3: ATTRIBUTES: Note functions that are thread-safe

[Zeng Linggang]

After research, We think getnetent_r(), getnetbyname_r() and
getnetbyaddr_r() 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/getnetent_r.3 | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/man3/getnetent_r.3 b/man3/getnetent_r.3
index 8f4c49f..d054fa3 100644
--- a/man3/getnetent_r.3
+++ b/man3/getnetent_r.3
@@ -138,6 +138,21 @@ is too small.
 Try again with a larger buffer
 (and increased
 .IR buflen ).
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw17 lb lb
+l l l.
+Interface	Attribute	Value
+T{
+.BR getnetent_r (),
+.BR getnetbyname_r (),
+.BR getnetbyaddr_r ()
+T}	Thread safety	MT-Safe locale
+.TE
+
 .SH CONFORMING TO
 These functions are GNU extensions.
 Functions with similar names exist on some 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] getnetent_r.3: ATTRIBUTES: Note functions that are thread-safe

[Michael Kerrisk (man-pages)]

On 05/27/2015 12:12 PM, Zeng Linggang wrote:
> After research, We think getnetent_r(), getnetbyname_r() and
> getnetbyaddr_r() 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/getnetent_r.3 | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
> 
> diff --git a/man3/getnetent_r.3 b/man3/getnetent_r.3
> index 8f4c49f..d054fa3 100644
> --- a/man3/getnetent_r.3
> +++ b/man3/getnetent_r.3
> @@ -138,6 +138,21 @@ is too small.
>  Try again with a larger buffer
>  (and increased
>  .IR buflen ).
> +.SH ATTRIBUTES
> +For an explanation of the terms used in this section, see
> +.BR attributes (7).
> +.TS
> +allbox;
> +lbw17 lb lb
> +l l l.
> +Interface	Attribute	Value
> +T{
> +.BR getnetent_r (),
> +.BR getnetbyname_r (),
> +.BR getnetbyaddr_r ()
> +T}	Thread safety	MT-Safe locale
> +.TE
> +
>  .SH CONFORMING TO
>  These functions are GNU extensions.
>  Functions with similar names exist on some 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] getpw.3: ATTRIBUTES: Note function that is thread-safe

[Zeng Linggang]

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

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

diff --git a/man3/getpw.3 b/man3/getpw.3
index 68402f1..21fb4e9 100644
--- a/man3/getpw.3
+++ b/man3/getpw.3
@@ -103,6 +103,19 @@ structure.
 .TP
 .I /etc/passwd
 password database file
+.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 getpw ()
+T}	Thread safety	MT-Safe locale
+.TE
+
 .SH CONFORMING TO
 SVr2.
 .SH BUGS
-- 
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] getpw.3: ATTRIBUTES: Note function that is thread-safe

[Michael Kerrisk (man-pages)]

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

Thanks, Zeng Linggang. Applied.

Cheers,

Michael

> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
>  man3/getpw.3 | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/man3/getpw.3 b/man3/getpw.3
> index 68402f1..21fb4e9 100644
> --- a/man3/getpw.3
> +++ b/man3/getpw.3
> @@ -103,6 +103,19 @@ structure.
>  .TP
>  .I /etc/passwd
>  password database file
> +.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 getpw ()
> +T}	Thread safety	MT-Safe locale
> +.TE
> +
>  .SH CONFORMING TO
>  SVr2.
>  .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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

[Zeng Linggang]

After research, We think key_decryptsession(), key_setsecret(),
key_encryptsession(), key_gendes() and key_secretkey_is_set() 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/key_setsecret.3 | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/man3/key_setsecret.3 b/man3/key_setsecret.3
index 426af3c..7c201ae 100644
--- a/man3/key_setsecret.3
+++ b/man3/key_setsecret.3
@@ -58,6 +58,27 @@ can be used to determine whether a key has been
 set for the effective UID of the calling process.
 .SH RETURN VALUE
 These functions return 1 on success and 0 on failure.
+.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 key_decryptsession (),
+.br
+.BR key_encryptsession (),
+.br
+.BR key_gendes (),
+.br
+.BR key_setsecret (),
+.br
+.BR key_secretkey_is_set ()
+T}	Thread safety	MT-Safe
+.TE
+
 .SH NOTES
 Note that we talk about two types of encryption here.
 One is asymmetric using a public and secret key.
-- 
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] key_setsecret.3: ATTRIBUTES: Note functions that are thread-safe

[Michael Kerrisk (man-pages)]

On 05/27/2015 12:12 PM, Zeng Linggang wrote:
> After research, We think key_decryptsession(), key_setsecret(),
> key_encryptsession(), key_gendes() and key_secretkey_is_set() 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/key_setsecret.3 | 21 +++++++++++++++++++++
>  1 file changed, 21 insertions(+)
> 
> diff --git a/man3/key_setsecret.3 b/man3/key_setsecret.3
> index 426af3c..7c201ae 100644
> --- a/man3/key_setsecret.3
> +++ b/man3/key_setsecret.3
> @@ -58,6 +58,27 @@ can be used to determine whether a key has been
>  set for the effective UID of the calling process.
>  .SH RETURN VALUE
>  These functions return 1 on success and 0 on failure.
> +.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 key_decryptsession (),
> +.br
> +.BR key_encryptsession (),
> +.br
> +.BR key_gendes (),
> +.br
> +.BR key_setsecret (),
> +.br
> +.BR key_secretkey_is_set ()
> +T}	Thread safety	MT-Safe
> +.TE
> +
>  .SH NOTES
>  Note that we talk about two types of encryption here.
>  One is asymmetric using a public and secret key.
> 


-- 
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] pthread_attr_setaffinity_np.3 ATTRIBUTES: Note functions that are thread-safe

[Zeng Linggang]

After research, We think pthread_attr_setaffinity_np() and
pthread_attr_getaffinity_np() 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/pthread_attr_setaffinity_np.3 | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/man3/pthread_attr_setaffinity_np.3 b/man3/pthread_attr_setaffinity_np.3
index ce49abb..cc6e94b 100644
--- a/man3/pthread_attr_setaffinity_np.3
+++ b/man3/pthread_attr_setaffinity_np.3
@@ -105,6 +105,20 @@ is too small).
 Could not allocate memory.
 .SH VERSIONS
 These functions are provided by glibc since version 2.3.4.
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw30 lb lb
+l l l.
+Interface	Attribute	Value
+T{
+.BR pthread_attr_setaffinity_np (),
+.BR pthread_attr_getaffinity_np ()
+T}	Thread safety	MT-Safe
+.TE
+
 .SH CONFORMING TO
 These functions are nonstandard GNU extensions;
 hence the suffix "_np" (nonportable) in the names.
-- 
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] pthread_attr_setaffinity_np.3 ATTRIBUTES: Note functions that are thread-safe

[Michael Kerrisk (man-pages)]

On 05/27/2015 12:12 PM, Zeng Linggang wrote:
> After research, We think pthread_attr_setaffinity_np() and
> pthread_attr_getaffinity_np() 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/pthread_attr_setaffinity_np.3 | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/man3/pthread_attr_setaffinity_np.3 b/man3/pthread_attr_setaffinity_np.3
> index ce49abb..cc6e94b 100644
> --- a/man3/pthread_attr_setaffinity_np.3
> +++ b/man3/pthread_attr_setaffinity_np.3
> @@ -105,6 +105,20 @@ is too small).
>  Could not allocate memory.
>  .SH VERSIONS
>  These functions are provided by glibc since version 2.3.4.
> +.SH ATTRIBUTES
> +For an explanation of the terms used in this section, see
> +.BR attributes (7).
> +.TS
> +allbox;
> +lbw30 lb lb
> +l l l.
> +Interface	Attribute	Value
> +T{
> +.BR pthread_attr_setaffinity_np (),
> +.BR pthread_attr_getaffinity_np ()
> +T}	Thread safety	MT-Safe
> +.TE
> +
>  .SH CONFORMING TO
>  These functions are nonstandard GNU extensions;
>  hence the suffix "_np" (nonportable) in the names.
> 


-- 
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] pthread_cleanup_push.3 ATTRIBUTES: Note functions that are thread-safe

[Zeng Linggang]

After research, We think pthread_cleanup_push() and
pthread_cleanup_pop() 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/pthread_cleanup_push.3 | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/man3/pthread_cleanup_push.3 b/man3/pthread_cleanup_push.3
index 43ac9b9..2b7fe05 100644
--- a/man3/pthread_cleanup_push.3
+++ b/man3/pthread_cleanup_push.3
@@ -124,6 +124,20 @@ These functions do not return a value.
 There are no errors.
 .\" SH VERSIONS
 .\" Available since glibc 2.0
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw23 lb lb
+l l l.
+Interface	Attribute	Value
+T{
+.BR pthread_cleanup_push (),
+.BR pthread_cleanup_pop ()
+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] pthread_cleanup_push.3 ATTRIBUTES: Note functions that are thread-safe

[Michael Kerrisk (man-pages)]

On 05/27/2015 12:13 PM, Zeng Linggang wrote:
> After research, We think pthread_cleanup_push() and
> pthread_cleanup_pop() 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/pthread_cleanup_push.3 | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/man3/pthread_cleanup_push.3 b/man3/pthread_cleanup_push.3
> index 43ac9b9..2b7fe05 100644
> --- a/man3/pthread_cleanup_push.3
> +++ b/man3/pthread_cleanup_push.3
> @@ -124,6 +124,20 @@ These functions do not return a value.
>  There are no errors.
>  .\" SH VERSIONS
>  .\" Available since glibc 2.0
> +.SH ATTRIBUTES
> +For an explanation of the terms used in this section, see
> +.BR attributes (7).
> +.TS
> +allbox;
> +lbw23 lb lb
> +l l l.
> +Interface	Attribute	Value
> +T{
> +.BR pthread_cleanup_push (),
> +.BR pthread_cleanup_pop ()
> +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

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

[Zeng Linggang]

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

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

diff --git a/man3/pthread_getattr_np.3 b/man3/pthread_getattr_np.3
index f721743..282d37c 100644
--- a/man3/pthread_getattr_np.3
+++ b/man3/pthread_getattr_np.3
@@ -95,6 +95,19 @@ if the
 resource limit is not supported.
 .SH VERSIONS
 This function is available in glibc since version 2.2.3.
+.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 pthread_getattr_np ()
+T}	Thread safety	MT-Safe
+.TE
+
 .SH CONFORMING TO
 This function is a nonstandard GNU extension;
 hence the suffix "_np" (nonportable) in the name.
-- 
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] pthread_getattr_np.3: ATTRIBUTES: Note function that is thread-safe

[Michael Kerrisk (man-pages)]

On 05/27/2015 12:13 PM, Zeng Linggang wrote:
> After research, We think pthread_getattr_np() is thread-safe. But,
> there is not marking of pthread_getattr_np() in glibc document.

Thanks, Zeng Linggang. Applied.

Cheers,

Michael


> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
>  man3/pthread_getattr_np.3 | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/man3/pthread_getattr_np.3 b/man3/pthread_getattr_np.3
> index f721743..282d37c 100644
> --- a/man3/pthread_getattr_np.3
> +++ b/man3/pthread_getattr_np.3
> @@ -95,6 +95,19 @@ if the
>  resource limit is not supported.
>  .SH VERSIONS
>  This function is available in glibc since version 2.2.3.
> +.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 pthread_getattr_np ()
> +T}	Thread safety	MT-Safe
> +.TE
> +
>  .SH CONFORMING TO
>  This function is a nonstandard GNU extension;
>  hence the suffix "_np" (nonportable) in the name.
> 


-- 
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] pthread_tryjoin_np.3 ATTRIBUTES: Note functions that are thread-safe

[Zeng Linggang]

After research, We think pthread_tryjoin_np() and
pthread_timedjoin_np() 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/pthread_tryjoin_np.3 | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/man3/pthread_tryjoin_np.3 b/man3/pthread_tryjoin_np.3
index 4fef86c..acce537 100644
--- a/man3/pthread_tryjoin_np.3
+++ b/man3/pthread_tryjoin_np.3
@@ -117,6 +117,20 @@ never returns the error
 .BR EINTR .
 .SH VERSIONS
 These functions first appeared in glibc in version 2.3.3.
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw22 lb lb
+l l l.
+Interface	Attribute	Value
+T{
+.BR pthread_tryjoin_np (),
+.BR pthread_timedjoin_np ()
+T}	Thread safety	MT-Safe
+.TE
+
 .SH CONFORMING TO
 These functions are nonstandard GNU extensions;
 hence the suffix "_np" (nonportable) in the names.
-- 
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] pthread_tryjoin_np.3 ATTRIBUTES: Note functions that are thread-safe

[Michael Kerrisk (man-pages)]

On 05/27/2015 12:13 PM, Zeng Linggang wrote:
> After research, We think pthread_tryjoin_np() and
> pthread_timedjoin_np() 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/pthread_tryjoin_np.3 | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/man3/pthread_tryjoin_np.3 b/man3/pthread_tryjoin_np.3
> index 4fef86c..acce537 100644
> --- a/man3/pthread_tryjoin_np.3
> +++ b/man3/pthread_tryjoin_np.3
> @@ -117,6 +117,20 @@ never returns the error
>  .BR EINTR .
>  .SH VERSIONS
>  These functions first appeared in glibc in version 2.3.3.
> +.SH ATTRIBUTES
> +For an explanation of the terms used in this section, see
> +.BR attributes (7).
> +.TS
> +allbox;
> +lbw22 lb lb
> +l l l.
> +Interface	Attribute	Value
> +T{
> +.BR pthread_tryjoin_np (),
> +.BR pthread_timedjoin_np ()
> +T}	Thread safety	MT-Safe
> +.TE
> +
>  .SH CONFORMING TO
>  These functions are nonstandard GNU extensions;
>  hence the suffix "_np" (nonportable) in the names.
> 


-- 
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] putgrent.3: ATTRIBUTES: Note function that is thread-safe

[Zeng Linggang]

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

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

diff --git a/man3/putgrent.3 b/man3/putgrent.3
index 4688c3a..de379ac 100644
--- a/man3/putgrent.3
+++ b/man3/putgrent.3
@@ -40,6 +40,19 @@ struct group {
 .in
 .SH RETURN VALUE
 The function returns zero on success, and a nonzero value on error.
+.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 putgrent ()
+T}	Thread safety	MT-Safe
+.TE
+
 .SH CONFORMING TO
 This function is a GNU extension.
 .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] putgrent.3: ATTRIBUTES: Note function that is thread-safe

[Michael Kerrisk (man-pages)]

On 05/27/2015 12:13 PM, Zeng Linggang wrote:
> After research, We think putgrent() is thread-safe. But, there
> is not marking of putgrent() in glibc document.


Thanks, Zeng Linggang. Applied.

Cheers,

Michael


> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
>  man3/putgrent.3 | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/man3/putgrent.3 b/man3/putgrent.3
> index 4688c3a..de379ac 100644
> --- a/man3/putgrent.3
> +++ b/man3/putgrent.3
> @@ -40,6 +40,19 @@ struct group {
>  .in
>  .SH RETURN VALUE
>  The function returns zero on success, and a nonzero value on error.
> +.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 putgrent ()
> +T}	Thread safety	MT-Safe
> +.TE
> +
>  .SH CONFORMING TO
>  This function is a GNU extension.
>  .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] xcrypt.3 ATTRIBUTES: Note functions that are thread-safe

[Zeng Linggang]

After research, We think passwd2des(), xencrypt() and xdecrypt() 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/xcrypt.3 | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/man3/xcrypt.3 b/man3/xcrypt.3
index 748bc88..0b9b419 100644
--- a/man3/xcrypt.3
+++ b/man3/xcrypt.3
@@ -66,6 +66,21 @@ and
 return 1 on success and 0 on error.
 .SH VERSIONS
 These functions are available in glibc since version 2.1.
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw12 lb lb
+l l l.
+Interface	Attribute	Value
+T{
+.BR passwd2des (),
+.BR xencrypt (),
+.BR xdecrypt ()
+T}	Thread safety	MT-Safe
+.TE
+
 .SH BUGS
 The prototypes are missing from the abovementioned include file.
 .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] xcrypt.3 ATTRIBUTES: Note functions that are thread-safe

[Michael Kerrisk (man-pages)]

On 05/27/2015 12:13 PM, Zeng Linggang wrote:
> After research, We think passwd2des(), xencrypt() and xdecrypt() 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/xcrypt.3 | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
> 
> diff --git a/man3/xcrypt.3 b/man3/xcrypt.3
> index 748bc88..0b9b419 100644
> --- a/man3/xcrypt.3
> +++ b/man3/xcrypt.3
> @@ -66,6 +66,21 @@ and
>  return 1 on success and 0 on error.
>  .SH VERSIONS
>  These functions are available in glibc since version 2.1.
> +.SH ATTRIBUTES
> +For an explanation of the terms used in this section, see
> +.BR attributes (7).
> +.TS
> +allbox;
> +lbw12 lb lb
> +l l l.
> +Interface	Attribute	Value
> +T{
> +.BR passwd2des (),
> +.BR xencrypt (),
> +.BR xdecrypt ()
> +T}	Thread safety	MT-Safe
> +.TE
> +
>  .SH BUGS
>  The prototypes are missing from the abovementioned include file.
>  .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

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

[Samuel Bronson]

On Wed, May 27, 2015 at 6:12 AM, Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org> wrote:
> After research, We think fexecve() is thread-safe. But, there
> is not marking of fexecve() in glibc document.

Um, fexecve() is just like execve(), only on a file descriptor.  (In
fact, it appears to be implemented using execve() on
/proc/self/fd/$FD.)

As such, the following point from execve(2) applies:

       *  All threads other than the calling thread are  destroyed  during  an
          execve().   Mutexes, condition variables, and other pthreads objects
          are not preserved.

This does not seem to correspond with the usual notion of "thread
safe", though I guess it would be technically safe to, say, have
several threads racing to run fexecve(). Further text is probably
warranted here.
--
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] fexecve.3: ATTRIBUTES: Note function that is thread-safe

[Michael Kerrisk (man-pages)]

Hi Zeng Linggang,

On 05/27/2015 05:42 PM, Samuel Bronson wrote:
> On Wed, May 27, 2015 at 6:12 AM, Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org> wrote:
>> After research, We think fexecve() is thread-safe. But, there
>> is not marking of fexecve() in glibc document.
> 
> Um, fexecve() is just like execve(), only on a file descriptor.  (In
> fact, it appears to be implemented using execve() on
> /proc/self/fd/$FD.)
> 
> As such, the following point from execve(2) applies:
> 
>        *  All threads other than the calling thread are  destroyed  during  an
>           execve().   Mutexes, condition variables, and other pthreads objects
>           are not preserved.
> 
> This does not seem to correspond with the usual notion of "thread
> safe", though I guess it would be technically safe to, say, have
> several threads racing to run fexecve(). Further text is probably
> warranted here.

Did you have any thoughts on Samuel's point?

Cheers,

Michael



-- 
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] fexecve.3: ATTRIBUTES: Note function that is thread-safe

[Zeng Linggang]

Hi,

On Fri, 2015-06-12 at 21:01 +0200, Michael Kerrisk (man-pages) wrote:
> Hi Zeng Linggang,
> 
> On 05/27/2015 05:42 PM, Samuel Bronson wrote:
> > On Wed, May 27, 2015 at 6:12 AM, Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org> wrote:
> >> After research, We think fexecve() is thread-safe. But, there
> >> is not marking of fexecve() in glibc document.
> > 
> > Um, fexecve() is just like execve(), only on a file descriptor.  (In
> > fact, it appears to be implemented using execve() on
> > /proc/self/fd/$FD.)
> > 
> > As such, the following point from execve(2) applies:
> > 
> >        *  All threads other than the calling thread are  destroyed  during  an
> >           execve().   Mutexes, condition variables, and other pthreads objects
> >           are not preserved.
> > 
> > This does not seem to correspond with the usual notion of "thread
> > safe", though I guess it would be technically safe to, say, have
> > several threads racing to run fexecve(). Further text is probably
> > warranted here.
> 
> Did you have any thoughts on Samuel's point?

Thanks for your remind, I almost miss it.

As we can see, the detail information has been list in 'execve'. I think
it is not necessary to add further text.

Best regards,
Zeng

> 
> Cheers,
> 
> Michael
> 
> 
> 


--
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] fexecve.3: ATTRIBUTES: Note function that is thread-safe

[Michael Kerrisk (man-pages)]

On 06/15/2015 05:58 AM, Zeng Linggang wrote:
> Hi,
> 
> On Fri, 2015-06-12 at 21:01 +0200, Michael Kerrisk (man-pages) wrote:
>> Hi Zeng Linggang,
>>
>> On 05/27/2015 05:42 PM, Samuel Bronson wrote:
>>> On Wed, May 27, 2015 at 6:12 AM, Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org> wrote:
>>>> After research, We think fexecve() is thread-safe. But, there
>>>> is not marking of fexecve() in glibc document.
>>>
>>> Um, fexecve() is just like execve(), only on a file descriptor.  (In
>>> fact, it appears to be implemented using execve() on
>>> /proc/self/fd/$FD.)
>>>
>>> As such, the following point from execve(2) applies:
>>>
>>>        *  All threads other than the calling thread are  destroyed  during  an
>>>           execve().   Mutexes, condition variables, and other pthreads objects
>>>           are not preserved.
>>>
>>> This does not seem to correspond with the usual notion of "thread
>>> safe", though I guess it would be technically safe to, say, have
>>> several threads racing to run fexecve(). Further text is probably
>>> warranted here.
>>
>> Did you have any thoughts on Samuel's point?
> 
> Thanks for your remind, I almost miss it.
> 
> As we can see, the detail information has been list in 'execve'. I think
> it is not necessary to add further text.

As long as you think it's okay, I'll go with that. I've
applied your patch.

Cheers,

Michael

-- 
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] fexecve.3: ATTRIBUTES: Note function that is thread-safe

[Zeng Linggang]

Hi!
On Wed, 2015-05-27 at 11:42 -0400, Samuel Bronson wrote:
> On Wed, May 27, 2015 at 6:12 AM, Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org> wrote:
> > After research, We think fexecve() is thread-safe. But, there
> > is not marking of fexecve() in glibc document.
> 
> Um, fexecve() is just like execve(), only on a file descriptor.  (In
> fact, it appears to be implemented using execve() on
> /proc/self/fd/$FD.)
> 

Sorry for the later.
Right. After gets the /proc/self/fd/$FD, it begins to using execve().

> As such, the following point from execve(2) applies:
> 
>        *  All threads other than the calling thread are  destroyed  during  an
>           execve().   Mutexes, condition variables, and other pthreads objects
>           are not preserved.
> 
> This does not seem to correspond with the usual notion of "thread
> safe", though I guess it would be technically safe to, say, have
> several threads racing to run fexecve(). Further text is probably
> warranted here.

Hmm, the detail information has been list in 'execve'. I think it is not
necessary to add further text.

Thanks and best regards,
Zeng

--
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