All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] pthread_atfork.3: Remove a confusing reference to the current thread
@ 2022-04-12 13:55 Arjun Shankar
  2022-04-12 14:31 ` Florian Weimer
  2022-04-13 18:34 ` Alejandro Colomar
  0 siblings, 2 replies; 6+ messages in thread
From: Arjun Shankar @ 2022-04-12 13:55 UTC (permalink / raw)
  To: linux-man; +Cc: Alejandro Colomar, Michael Kerrisk

The reference to "this thread" in the DESCRIPTION of pthread_atfork(3)
could be incorrectly interpreted to mean that only handlers registered
by the thread calling fork(2) are executed.  Therefore, remove the
reference.

Signed-off-by: Arjun Shankar <arjun@redhat.com>
---
 man3/pthread_atfork.3 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man3/pthread_atfork.3 b/man3/pthread_atfork.3
index b727cb48e..db5e210d4 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.
 The handlers are executed in the context of the thread that calls
 .BR fork (2).
 .PP
-- 
2.34.1


^ permalink raw reply related	[flat|nested] 6+ messages in thread

* Re: [PATCH] pthread_atfork.3: Remove a confusing reference to the current thread
  2022-04-12 13:55 [PATCH] pthread_atfork.3: Remove a confusing reference to the current thread Arjun Shankar
@ 2022-04-12 14:31 ` Florian Weimer
  2022-04-12 15:10   ` Arjun Shankar
  2022-04-13 18:34 ` Alejandro Colomar
  1 sibling, 1 reply; 6+ messages in thread
From: Florian Weimer @ 2022-04-12 14:31 UTC (permalink / raw)
  To: Arjun Shankar; +Cc: linux-man, Alejandro Colomar, Michael Kerrisk

* Arjun Shankar:

> The reference to "this thread" in the DESCRIPTION of pthread_atfork(3)
> could be incorrectly interpreted to mean that only handlers registered
> by the thread calling fork(2) are executed.  Therefore, remove the
> reference.
>
> Signed-off-by: Arjun Shankar <arjun@redhat.com>
> ---
>  man3/pthread_atfork.3 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man3/pthread_atfork.3 b/man3/pthread_atfork.3
> index b727cb48e..db5e210d4 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.
>  The handlers are executed in the context of the thread that calls
>  .BR fork (2).
>  .PP

I suspect the intent was to indicate that the handlers are called on the
thread calling fork, but that's probably clear enough from the context?

Thanks,
Florian


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] pthread_atfork.3: Remove a confusing reference to the current thread
  2022-04-12 14:31 ` Florian Weimer
@ 2022-04-12 15:10   ` Arjun Shankar
  0 siblings, 0 replies; 6+ messages in thread
From: Arjun Shankar @ 2022-04-12 15:10 UTC (permalink / raw)
  To: Florian Weimer; +Cc: linux-man, Alejandro Colomar, Michael Kerrisk

> I suspect the intent was to indicate that the handlers are called on the
> thread calling fork, but that's probably clear enough from the context?

Yes, that could have been the intent. It is also mentioned separately
in the second sentence, so that information will not be lost if this
change gets applied.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] pthread_atfork.3: Remove a confusing reference to the current thread
  2022-04-12 13:55 [PATCH] pthread_atfork.3: Remove a confusing reference to the current thread Arjun Shankar
  2022-04-12 14:31 ` Florian Weimer
@ 2022-04-13 18:34 ` Alejandro Colomar
  2022-04-13 23:51   ` Arjun Shankar
  1 sibling, 1 reply; 6+ messages in thread
From: Alejandro Colomar @ 2022-04-13 18:34 UTC (permalink / raw)
  To: Arjun Shankar, linux-man; +Cc: Michael Kerrisk, Florian Weimer


[-- Attachment #1.1: Type: text/plain, Size: 1328 bytes --]

Hi Arjun,

On 4/12/22 15:55, Arjun Shankar wrote:
> The reference to "this thread" in the DESCRIPTION of pthread_atfork(3)
> could be incorrectly interpreted to mean that only handlers registered
> by the thread calling fork(2) are executed.  Therefore, remove the
> reference.
> 
> Signed-off-by: Arjun Shankar <arjun@redhat.com>

I already applied a different patch recently.  See 
<http://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/man3/pthread_atfork.3?id=f30deb08a9a0db95a3d6b4d00c0927fb43928cc4>.

If you think that can be improved, please send a patch on top of the 
main branch in that repo.

Thanks,

Alex
> ---
>   man3/pthread_atfork.3 | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/man3/pthread_atfork.3 b/man3/pthread_atfork.3
> index b727cb48e..db5e210d4 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.
>   The handlers are executed in the context of the thread that calls
>   .BR fork (2).
>   .PP


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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] pthread_atfork.3: Remove a confusing reference to the current thread
  2022-04-13 18:34 ` Alejandro Colomar
@ 2022-04-13 23:51   ` Arjun Shankar
  2022-04-25 20:21     ` Alejandro Colomar
  0 siblings, 1 reply; 6+ messages in thread
From: Arjun Shankar @ 2022-04-13 23:51 UTC (permalink / raw)
  To: Alejandro Colomar; +Cc: linux-man, Michael Kerrisk, Florian Weimer

Hi Alex,

> I already applied a different patch recently.  See
> <http://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/man3/pthread_atfork.3?id=f30deb08a9a0db95a3d6b4d00c0927fb43928cc4>.

I wasn't aware of this repository and therefore missed the change.
I'll keep it in mind.

> If you think that can be improved, please send a patch on top of the
> main branch in that repo.

The commit you mentioned looks good to me. Apologies for the noise and
thanks for looking into this.

Cheers,
Arjun


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] pthread_atfork.3: Remove a confusing reference to the current thread
  2022-04-13 23:51   ` Arjun Shankar
@ 2022-04-25 20:21     ` Alejandro Colomar
  0 siblings, 0 replies; 6+ messages in thread
From: Alejandro Colomar @ 2022-04-25 20:21 UTC (permalink / raw)
  To: Arjun Shankar; +Cc: linux-man, Michael Kerrisk, Florian Weimer

Hi Arjun,

On 4/14/22 01:51, Arjun Shankar wrote:
> Hi Alex,
> 
>> I already applied a different patch recently.  See
>> <http://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/man3/pthread_atfork.3?id=f30deb08a9a0db95a3d6b4d00c0927fb43928cc4>.
> 
> I wasn't aware of this repository and therefore missed the change.
> I'll keep it in mind. >
>> If you think that can be improved, please send a patch on top of the
>> main branch in that repo.
> 
> The commit you mentioned looks good to me. Apologies for the noise and
> thanks for looking into this.

No problem.  It's not noise, IMO :-)
It's always nice to have more wording options to consider.

Cheers,

Alex

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2022-04-25 20:21 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-04-12 13:55 [PATCH] pthread_atfork.3: Remove a confusing reference to the current thread Arjun Shankar
2022-04-12 14:31 ` Florian Weimer
2022-04-12 15:10   ` Arjun Shankar
2022-04-13 18:34 ` Alejandro Colomar
2022-04-13 23:51   ` Arjun Shankar
2022-04-25 20:21     ` Alejandro Colomar

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.