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 v2] getlogin.3: ATTRIBUTES: Note function that is not thread-safe
Date: Mon, 27 May 2013 04:55:21 +0200 [thread overview]
Message-ID: <51A2CB19.9000802@gmail.com> (raw)
In-Reply-To: <1369357689-9069-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
On 05/24/13 03:08, Peng Haitao wrote:
> The function getlogin() is not thread safe.
> The function cuserid() is thread-safe with exceptions.
Thanks Peng. Applied in my local branch.
Cheers,
Michael
> Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
> man3/getlogin.3 | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/man3/getlogin.3 b/man3/getlogin.3
> index be7cc87..7050d5d 100644
> --- a/man3/getlogin.3
> +++ b/man3/getlogin.3
> @@ -135,6 +135,20 @@ password database file
> \fI/var/run/utmp\fP
> (traditionally \fI/etc/utmp\fP;
> some libc versions used \fI/var/adm/utmp\fP)
> +.SH ATTRIBUTES
> +.SS Multithreading(see pthreads(7))
> +The
> +.BR getlogin ()
> +function is not thread-safe.
> +.LP
> +The
> +.BR getlogin_r ()
> +function is thread-safe.
> +.LP
> +The
> +.BR cuserid ()
> +function is thread-safe with exceptions.
> +It is not thread-safe if called with a NULL parameter.
> .SH CONFORMING TO
> .BR getlogin ()
> and
>
--
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
prev parent reply other threads:[~2013-05-27 2:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 1:08 [PATCH v2] getlogin.3: ATTRIBUTES: Note function that is not thread-safe Peng Haitao
[not found] ` <1369357689-9069-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-05-27 2:55 ` 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=51A2CB19.9000802@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.