linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Cc: carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org,
	aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] getusershell.3: ATTRIBUTES: Note functions that are not thread-safe
Date: Thu, 30 May 2013 13:03:28 +0200	[thread overview]
Message-ID: <51A73200.5060706@gmail.com> (raw)
In-Reply-To: <1369734610-12284-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>

On 05/28/13 11:50, Peng Haitao wrote:
> The functions getusershell(), setusershell() and endusershell()
> are not thread safe.

Thanks, Peng. Applied in my local branch.

Cheers,

Michael


> Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
>  man3/getusershell.3 | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/man3/getusershell.3 b/man3/getusershell.3
> index a6c8ab1..b9e7e58 100644
> --- a/man3/getusershell.3
> +++ b/man3/getusershell.3
> @@ -82,6 +82,14 @@ function returns a NULL pointer on end-of-file.
>  .nf
>  /etc/shells
>  .fi
> +.SH ATTRIBUTES
> +.SS Multithreading (see pthreads(7))
> +The
> +.BR getusershell (),
> +.BR setusershell ()
> +and
> +.BR endusershell ()
> +functions are not thread-safe.
>  .SH CONFORMING TO
>  4.3BSD.
>  .SH SEE ALSO
> 

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

      parent reply	other threads:[~2013-05-30 11:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28  9:50 [PATCH] getusershell.3: ATTRIBUTES: Note functions that are not thread-safe Peng Haitao
     [not found] ` <1369734610-12284-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-05-28 14:06   ` Michael Kerrisk
2013-05-30 11:03   ` Michael Kerrisk [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51A73200.5060706@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).