public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: enh <enh@google.com>
Cc: linux-man <linux-man@vger.kernel.org>,
	"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
	Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH] pthread_atfork.3: wfix.
Date: Thu, 11 Nov 2021 22:49:34 +0100	[thread overview]
Message-ID: <9dcab95b-ec77-b82b-22cf-ce082af033fb@gmail.com> (raw)
In-Reply-To: <874k8k8m5s.fsf@oldenburg.str.redhat.com>

Hi,

On 11/9/21 23:27, enh wrote:
 > Clarify that the pthread_atfork() callback list is a global, not
 > per-thread.
 >
 > The use of "this thread" implied to some readers that pthread_atfork()
 > maintained per-thread lists of callbacks. Given that the next sentence
 > already explains that the callbacks are run in the context of the thread
 > that calls fork(), I actually think it would be fine not to mention
 > threads at all in the earlier sentence, but for now I've gone with what
 > I think was intended to be written.
 > ---
 >   man3/pthread_atfork.3 | 2 +-
 >   1 file changed, 1 insertion(+), 1 deletion(-)

Could you please sign your patch?

<https://www.kernel.org/doc/html/latest/process/submitting-patches.html#developer-s-certificate-of-origin-1-1>

On 11/10/21 09:11, Florian Weimer wrote:
>> 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.

Also, if you could also fix that line reported by Florian in the same 
patch, it would be great.

Thanks!

Alex

-- 
Alejandro Colomar
Linux man-pages comaintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

  reply	other threads:[~2021-11-11 21:49 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
2021-11-11 21:49   ` Alejandro Colomar (man-pages) [this message]
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=9dcab95b-ec77-b82b-22cf-ce082af033fb@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=enh@google.com \
    --cc=fweimer@redhat.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