From: Florian Weimer <fweimer@redhat.com>
To: enh <enh@google.com>
Cc: linux-man <linux-man@vger.kernel.org>,
"Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Subject: Re: [PATCH] pthread_atfork.3: wfix.
Date: Wed, 10 Nov 2021 09:11:59 +0100 [thread overview]
Message-ID: <874k8k8m5s.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAJgzZoqZ1yfFtP0Zbc+i5aGS1bn6VJu2dHaa9CJhJr2P7QfSiQ@mail.gmail.com> (enh@google.com's message of "Tue, 9 Nov 2021 14:27:59 -0800")
> diff --git a/man3/pthread_atfork.3 b/man3/pthread_atfork.3
> index b727cb48e..3e61e797f 100644
> --- a/man3/pthread_atfork.3
> +++ b/man3/pthread_atfork.3
> @@ -39,7 +39,7 @@ The
> .BR pthread_atfork ()
> function registers fork handlers that are to be executed when
> .BR fork (2)
> -is called by this thread.
> +is called by any thread in a process.
> The handlers are executed in the context of the thread that calls
> .BR fork (2).
> .PP
There's another confusing “thread” reference further below:
“pthread_atfork() may be called multiple times by a thread, to register
multiple handlers for each phase.” I think that should be replaced by
“process” for clarity.
Thanks,
Florian
next prev parent reply other threads:[~2021-11-10 8:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 22:27 [PATCH] pthread_atfork.3: wfix enh
2021-11-10 8:11 ` Florian Weimer [this message]
2021-11-11 21:49 ` Alejandro Colomar (man-pages)
2021-11-11 22:42 ` enh
2021-11-22 17:02 ` Alejandro Colomar (man-pages)
[not found] ` <CAJgzZoqDAMuk8j-kwzxkKMSbs4z2ZiGzbQuUkrouXitgW+RYmg@mail.gmail.com>
2022-07-26 11:06 ` Alejandro Colomar
2022-07-26 17:09 ` enh
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=874k8k8m5s.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=alx.manpages@gmail.com \
--cc=enh@google.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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