Thanks, Haitao! Applied. Cheers, Michael On 03/24/2014 09:43 AM, penght@xxxxxxxxxxxxxx wrote: > The functions sigvec(), sigblock(), sigsetmask() and > siggetmask() are thread safe. > > The macro sigmask() is thread safe. > > Signed-off-by: Peng Haitao <penght@xxxxxxxxxxxxxx> > --- > man3/sigvec.3 | 15 ++++++++++++++- > 1 file changed, 14 insertions(+), 1 deletion(-) > > diff --git a/man3/sigvec.3 b/man3/sigvec.3 > index 28f580c..39b39f9 100644 > --- a/man3/sigvec.3 > +++ b/man3/sigvec.3 > @@ -23,7 +23,7 @@ > .\" the source, must acknowledge the copyright and authors of this work. > .\" %%%LICENSE_END > .\" > -.TH SIGVEC 3 2014-02-18 "Linux" "Linux Programmer's Manual" > +.TH SIGVEC 3 2014-03-24 "Linux" "Linux Programmer's Manual" > .SH NAME > sigvec, sigblock, sigsetmask, siggetmask, sigmask \- BSD signal API > .SH SYNOPSIS > @@ -218,6 +218,19 @@ See the ERRORS under > .BR sigaction (2) > and > .BR sigprocmask (2). > +.SH ATTRIBUTES > +.SS Multithreading (see pthreads(7)) > +The > +.BR sigvec (), > +.BR sigblock (), > +.BR sigsetmask (), > +and > +.BR siggetmask () > +functions are thread-safe. > +.LP > +The > +.BR sigmask () > +macro is thread-safe. > .SH CONFORMING TO > All of these functions were in > 4.3BSD, except > -- 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
