[PATCH] clock_getres.2: ATTRIBUTES: Note functions that are thread-safe

[PATCH] clock_getres.2: ATTRIBUTES: Note functions that are thread-safe

[Zeng Linggang]

After research, We think clock_getres(), clock_gettime() and
clock_settime() are thread-safe. But, there are not markings of
clock_getres(), clock_gettime() and clock_settime() in glibc document.

Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
---
 man2/clock_getres.2 | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/man2/clock_getres.2 b/man2/clock_getres.2
index 6809c7b..c7ecd3d 100644
--- a/man2/clock_getres.2
+++ b/man2/clock_getres.2
@@ -204,6 +204,21 @@ specified is not supported on this system.
 does not have permission to set the clock indicated.
 .SH VERSIONS
 These system calls first appeared in Linux 2.6.
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw16 lb lb
+l l l.
+Interface	Attribute	Value
+T{
+.BR clock_getres (),
+.BR clock_gettime (),
+.BR clock_settime ()
+T}	Thread safety	MT-Safe
+.TE
+
 .SH CONFORMING TO
 SUSv2, POSIX.1-2001.
 .SH AVAILABILITY
-- 
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] eventfd.2: ATTRIBUTES: Note function that is thread-safe

[Zeng Linggang]

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

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

diff --git a/man2/eventfd.2 b/man2/eventfd.2
index 01c2d87..6b37e2d 100644
--- a/man2/eventfd.2
+++ b/man2/eventfd.2
@@ -263,6 +263,19 @@ Since version 2.9, the glibc
 wrapper will employ the
 .BR eventfd2 ()
 system call, if it is supported by the kernel.
+.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 eventfd ()
+T}	Thread safety	MT-Safe
+.TE
+
 .SH CONFORMING TO
 .BR eventfd ()
 and
-- 
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] fpurge.3: ATTRIBUTES: Note function that is thread-safe

[Zeng Linggang]

The marking matches glibc marking.
The marking of functions in glibc is:
- __fpurge: MT-Safe race:stream

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

diff --git a/man3/fpurge.3 b/man3/fpurge.3
index 70a52bc..64fce05 100644
--- a/man3/fpurge.3
+++ b/man3/fpurge.3
@@ -67,6 +67,19 @@ appropriately.
 .B EBADF
 .I stream
 is not an open stream.
+.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 __fpurge ()
+T}	Thread safety	MT-Safe race:stream
+.TE
+
 .SH CONFORMING TO
 These functions are nonstandard and not portable.
 The function
-- 
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] pthread_attr_init.3: ATTRIBUTES: Note functions that are thread-safe

[Zeng Linggang]

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

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

diff --git a/man3/pthread_attr_init.3 b/man3/pthread_attr_init.3
index 3875519..21745c0 100644
--- a/man3/pthread_attr_init.3
+++ b/man3/pthread_attr_init.3
@@ -76,6 +76,20 @@ error for
 on Linux these functions always succeed
 (but portable and future-proof applications should nevertheless
 handle a possible error return).
+.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_attr_init (),
+.BR pthread_attr_destroy ()
+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

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

[Zeng Linggang]

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

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

diff --git a/man3/pthread_cancel.3 b/man3/pthread_cancel.3
index 6317ede..1c8dd91 100644
--- a/man3/pthread_cancel.3
+++ b/man3/pthread_cancel.3
@@ -122,6 +122,19 @@ No thread with the ID
 could be found.
 .\" .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;
+lb lb lb
+l l l.
+Interface	Attribute	Value
+T{
+.BR pthread_cancel ()
+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

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

[Zeng Linggang]

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

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

diff --git a/man3/pthread_create.3 b/man3/pthread_create.3
index 82f73e1..b04699b 100644
--- a/man3/pthread_create.3
+++ b/man3/pthread_create.3
@@ -150,6 +150,19 @@ Invalid settings in
 .B EPERM
 No permission to set the scheduling policy and parameters specified in
 .IR attr .
+.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_create ()
+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

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

[Zeng Linggang]

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

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

diff --git a/man3/pthread_detach.3 b/man3/pthread_detach.3
index 43f6885..f6d37d7 100644
--- a/man3/pthread_detach.3
+++ b/man3/pthread_detach.3
@@ -61,6 +61,19 @@ is not a joinable thread.
 No thread with the ID
 .I thread
 could be found.
+.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_detach ()
+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

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

[Zeng Linggang]

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

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

diff --git a/man3/pthread_join.3 b/man3/pthread_join.3
index 00eafb9..3340172 100644
--- a/man3/pthread_join.3
+++ b/man3/pthread_join.3
@@ -95,6 +95,19 @@ Another thread is already waiting to join with this thread.
 No thread with the ID
 .I thread
 could be found.
+.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_join ()
+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

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

[Zeng Linggang]

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

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

diff --git a/man3/pthread_setname_np.3 b/man3/pthread_setname_np.3
index b9c0487..ef90fa1 100644
--- a/man3/pthread_setname_np.3
+++ b/man3/pthread_setname_np.3
@@ -99,6 +99,20 @@ then the call may fail with one of the errors described in
 .BR open (2).
 .SH VERSIONS
 These functions first appeared in glibc in version 2.12.
+.SH ATTRIBUTES
+For an explanation of the terms used in this section, see
+.BR attributes (7).
+.TS
+allbox;
+lbw21 lb lb
+l l l.
+Interface	Attribute	Value
+T{
+.BR pthread_setname_np (),
+.BR pthread_getname_np ()
+T}	Thread safety	MT-Safe
+.TE
+
 .SH CONFORMING TO
 These functions are nonstandard 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

[PATCH] utimensat.2: ATTRIBUTES: Note functions that are thread-safe

[Zeng Linggang]

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

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

diff --git a/man2/utimensat.2 b/man2/utimensat.2
index 80094d7..1dc941a 100644
--- a/man2/utimensat.2
+++ b/man2/utimensat.2
@@ -418,6 +418,20 @@ glibc support was added with version 2.6.
 Support for
 .BR futimens ()
 first appeared in glibc 2.6.
+.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 utimensat (),
+.BR futimens ()
+T}	Thread safety	MT-Safe
+.TE
+
 .SH CONFORMING TO
 .BR futimens ()
 and
-- 
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] clock_getres.2: ATTRIBUTES: Note functions that are thread-safe

[Michael Kerrisk (man-pages)]

On 05/20/2015 12:00 PM, Zeng Linggang wrote:
> After research, We think clock_getres(), clock_gettime() and
> clock_settime() are thread-safe. But, there are not markings of
> clock_getres(), clock_gettime() and clock_settime() in glibc document.
> 
> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>

Thanks, Zeng Linggang. Patch applied.

Cheers,

Michael


> ---
>  man2/clock_getres.2 | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
> 
> diff --git a/man2/clock_getres.2 b/man2/clock_getres.2
> index 6809c7b..c7ecd3d 100644
> --- a/man2/clock_getres.2
> +++ b/man2/clock_getres.2
> @@ -204,6 +204,21 @@ specified is not supported on this system.
>  does not have permission to set the clock indicated.
>  .SH VERSIONS
>  These system calls first appeared in Linux 2.6.
> +.SH ATTRIBUTES
> +For an explanation of the terms used in this section, see
> +.BR attributes (7).
> +.TS
> +allbox;
> +lbw16 lb lb
> +l l l.
> +Interface	Attribute	Value
> +T{
> +.BR clock_getres (),
> +.BR clock_gettime (),
> +.BR clock_settime ()
> +T}	Thread safety	MT-Safe
> +.TE
> +
>  .SH CONFORMING TO
>  SUSv2, POSIX.1-2001.
>  .SH AVAILABILITY
> 


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

[Michael Kerrisk (man-pages)]

On 05/20/2015 12:00 PM, Zeng Linggang wrote:
> After research, We think eventfd() is thread-safe. But, there
> is not marking of eventfd() in glibc document.
> 
> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>


Thanks, Zeng Linggang. Patch applied.

Cheers,

Michael



> ---
>  man2/eventfd.2 | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/man2/eventfd.2 b/man2/eventfd.2
> index 01c2d87..6b37e2d 100644
> --- a/man2/eventfd.2
> +++ b/man2/eventfd.2
> @@ -263,6 +263,19 @@ Since version 2.9, the glibc
>  wrapper will employ the
>  .BR eventfd2 ()
>  system call, if it is supported by the kernel.
> +.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 eventfd ()
> +T}	Thread safety	MT-Safe
> +.TE
> +
>  .SH CONFORMING TO
>  .BR eventfd ()
>  and
> 


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

[Michael Kerrisk (man-pages)]

On 05/20/2015 12:00 PM, Zeng Linggang wrote:
> The marking matches glibc marking.
> The marking of functions in glibc is:
> - __fpurge: MT-Safe race:stream
> 
> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>

Thanks, Zeng Linggang. Patch applied.

Cheers,

Michael


> ---
>  man3/fpurge.3 | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/man3/fpurge.3 b/man3/fpurge.3
> index 70a52bc..64fce05 100644
> --- a/man3/fpurge.3
> +++ b/man3/fpurge.3
> @@ -67,6 +67,19 @@ appropriately.
>  .B EBADF
>  .I stream
>  is not an open stream.
> +.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 __fpurge ()
> +T}	Thread safety	MT-Safe race:stream
> +.TE
> +
>  .SH CONFORMING TO
>  These functions are nonstandard and not portable.
>  The function
> 


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

[Michael Kerrisk (man-pages)]

On 05/20/2015 12:00 PM, Zeng Linggang wrote:
> After research, We think pthread_attr_init() and pthread_attr_destroy()
> are thread-safe. But, there are not markings of pthread_attr_init()
> and pthread_attr_destroy() in glibc document.
> 
> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>

Thanks, Zeng Linggang. Patch applied.

Cheers,

Michael


> ---
>  man3/pthread_attr_init.3 | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/man3/pthread_attr_init.3 b/man3/pthread_attr_init.3
> index 3875519..21745c0 100644
> --- a/man3/pthread_attr_init.3
> +++ b/man3/pthread_attr_init.3
> @@ -76,6 +76,20 @@ error for
>  on Linux these functions always succeed
>  (but portable and future-proof applications should nevertheless
>  handle a possible error return).
> +.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_attr_init (),
> +.BR pthread_attr_destroy ()
> +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] pthread_cancel.3: ATTRIBUTES: Note function that is thread-safe

[Michael Kerrisk (man-pages)]

On 05/20/2015 12:00 PM, Zeng Linggang wrote:
> After research, We think pthread_cancel() is thread-safe. But, there
> is not marking of pthread_cancel() in glibc document.
> 
> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>


Thanks, Zeng Linggang. Patch applied.

Cheers,

Michael




> ---
>  man3/pthread_cancel.3 | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/man3/pthread_cancel.3 b/man3/pthread_cancel.3
> index 6317ede..1c8dd91 100644
> --- a/man3/pthread_cancel.3
> +++ b/man3/pthread_cancel.3
> @@ -122,6 +122,19 @@ No thread with the ID
>  could be found.
>  .\" .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;
> +lb lb lb
> +l l l.
> +Interface	Attribute	Value
> +T{
> +.BR pthread_cancel ()
> +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] pthread_create.3: ATTRIBUTES: Note function that is thread-safe

[Michael Kerrisk (man-pages)]

On 05/20/2015 12:00 PM, Zeng Linggang wrote:
> After research, We think pthread_create() is thread-safe. But, there
> is not marking of pthread_create() in glibc document.
> 
> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>

Thanks, Zeng Linggang. Patch applied.

Cheers,

Michael


> ---
>  man3/pthread_create.3 | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/man3/pthread_create.3 b/man3/pthread_create.3
> index 82f73e1..b04699b 100644
> --- a/man3/pthread_create.3
> +++ b/man3/pthread_create.3
> @@ -150,6 +150,19 @@ Invalid settings in
>  .B EPERM
>  No permission to set the scheduling policy and parameters specified in
>  .IR attr .
> +.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_create ()
> +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] pthread_detach.3: ATTRIBUTES: Note function that is thread-safe

[Michael Kerrisk (man-pages)]

On 05/20/2015 12:00 PM, Zeng Linggang wrote:
> After research, We think pthread_detach() is thread-safe. But, there
> is not marking of pthread_detach() in glibc document.
> 
> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>

Thanks, Zeng Linggang. Patch applied.

Cheers,

Michael


> ---
>  man3/pthread_detach.3 | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/man3/pthread_detach.3 b/man3/pthread_detach.3
> index 43f6885..f6d37d7 100644
> --- a/man3/pthread_detach.3
> +++ b/man3/pthread_detach.3
> @@ -61,6 +61,19 @@ is not a joinable thread.
>  No thread with the ID
>  .I thread
>  could be found.
> +.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_detach ()
> +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] pthread_join.3: ATTRIBUTES: Note function that is thread-safe

[Michael Kerrisk (man-pages)]

On 05/20/2015 12:00 PM, Zeng Linggang wrote:
> After research, We think pthread_join() is thread-safe. But, there
> is not marking of pthread_join() in glibc document.
> 
> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>


Thanks, Zeng Linggang. Patch applied.

Cheers,

Michael



> ---
>  man3/pthread_join.3 | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/man3/pthread_join.3 b/man3/pthread_join.3
> index 00eafb9..3340172 100644
> --- a/man3/pthread_join.3
> +++ b/man3/pthread_join.3
> @@ -95,6 +95,19 @@ Another thread is already waiting to join with this thread.
>  No thread with the ID
>  .I thread
>  could be found.
> +.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_join ()
> +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] pthread_setname_np.3: ATTRIBUTES: Note functions that are thread-safe

[Michael Kerrisk (man-pages)]

On 05/20/2015 12:00 PM, Zeng Linggang wrote:
> After research, We think pthread_setname_np() and pthread_getname_np()
> are thread-safe. But, there are not markings of pthread_setname_np()
> and pthread_getname_np() in glibc document.
> 
> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>


Thanks, Zeng Linggang. Patch applied.

Cheers,

Michael



> ---
>  man3/pthread_setname_np.3 | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/man3/pthread_setname_np.3 b/man3/pthread_setname_np.3
> index b9c0487..ef90fa1 100644
> --- a/man3/pthread_setname_np.3
> +++ b/man3/pthread_setname_np.3
> @@ -99,6 +99,20 @@ then the call may fail with one of the errors described in
>  .BR open (2).
>  .SH VERSIONS
>  These functions first appeared in glibc in version 2.12.
> +.SH ATTRIBUTES
> +For an explanation of the terms used in this section, see
> +.BR attributes (7).
> +.TS
> +allbox;
> +lbw21 lb lb
> +l l l.
> +Interface	Attribute	Value
> +T{
> +.BR pthread_setname_np (),
> +.BR pthread_getname_np ()
> +T}	Thread safety	MT-Safe
> +.TE
> +
>  .SH CONFORMING TO
>  These functions are nonstandard 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

Re: [PATCH] utimensat.2: ATTRIBUTES: Note functions that are thread-safe

[Michael Kerrisk (man-pages)]

On 05/20/2015 12:00 PM, Zeng Linggang wrote:
> After research, We think utimensat() and futimens() are thread-safe.
> But, there are not markings of utimensat() and futimens() in glibc
> document.
> 
> Signed-off-by: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>

Thanks, Zeng Linggang. Patch applied.

Cheers,

Michael


> ---
>  man2/utimensat.2 | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/man2/utimensat.2 b/man2/utimensat.2
> index 80094d7..1dc941a 100644
> --- a/man2/utimensat.2
> +++ b/man2/utimensat.2
> @@ -418,6 +418,20 @@ glibc support was added with version 2.6.
>  Support for
>  .BR futimens ()
>  first appeared in glibc 2.6.
> +.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 utimensat (),
> +.BR futimens ()
> +T}	Thread safety	MT-Safe
> +.TE
> +
>  .SH CONFORMING TO
>  .BR futimens ()
>  and
> 


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