From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org,
aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH] exit.3: ATTRIBUTES: Note function that is not thread-safe
Date: Sat, 18 May 2013 20:30:28 +0200 [thread overview]
Message-ID: <5197C8C4.3060205@gmail.com> (raw)
In-Reply-To: <1367572694-21931-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Hello Peng,
NOTE: I have not yet applied this patch. See comments below.
On 05/03/13 11:18, Peng Haitao wrote:
> The function exit() is not thread safe.
>
> Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
> man3/exit.3 | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/man3/exit.3 b/man3/exit.3
> index 51163e4..5e607b1 100644
> --- a/man3/exit.3
> +++ b/man3/exit.3
> @@ -87,6 +87,11 @@ termination, respectively.
> The
> .BR exit ()
> function does not return.
> +.SH ATTRIBUTES
> +.SS Multithreading (see pthreads(7))
> +The
> +.BR exit ()
> +uses a global variable that is not protected, so it is not thread-safe.
Ouch! Really? so one cannot call exit(3) from a multithreaded program?
This seems a clear violation of the standard.
Could you provide some pointers to more information on this point (e.g., URL
of mail thread archive discussions.)
Thanks,
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
next prev parent reply other threads:[~2013-05-18 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 9:18 [PATCH] exit.3: ATTRIBUTES: Note function that is not thread-safe Peng Haitao
[not found] ` <1367572694-21931-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-05-18 18:30 ` Michael Kerrisk [this message]
[not found] ` <5197C8C4.3060205-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-05-20 2:30 ` Peng Haitao
[not found] ` <51998AC5.3070803-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2014-03-25 2:56 ` penght-BthXqXjhjHXQFUHtdCDX3A
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=5197C8C4.3060205@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.