[PATCH] clone.2: Clarify the behaviour of exit_signal with CLONE_PARENT

[PATCH] clone.2: Clarify the behaviour of exit_signal with CLONE_PARENT

[Sargun Dhillon]

It's documented under ERRORS that specifying a exit_signal with CLONE_PARENT
is not allowed, but it is not specified how the exit_signal is to be set
(or is set) when using the CLONE_PARENT flag.

Signed-off-by: Sargun Dhillon <sargun@sargun.me>
---
 man2/clone.2 | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/man2/clone.2 b/man2/clone.2
index 4c5b4ac6b..0b2a60482 100644
--- a/man2/clone.2
+++ b/man2/clone.2
@@ -290,7 +290,13 @@ The termination signal is specified in the low byte of
 .RB ( clone ())
 or in
 .I cl_args.exit_signal
-.RB ( clone3 ()).
+.RB ( clone3 ()),
+unless
+.BR CLONE_PARENT
+flag is set. If the
+.BR CLONE_PARENT
+flag is set, then the exit_signal is copied from the calling process's process
+group leader.
 If this signal is specified as anything other than
 .BR SIGCHLD ,
 then the parent process must specify the
-- 
2.39.3

Re: [PATCH] clone.2: Clarify the behaviour of exit_signal with CLONE_PARENT

[Alejandro Colomar]

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

Hello Sargun,

On 2023-08-10 03:34, Sargun Dhillon wrote:
> It's documented under ERRORS that specifying a exit_signal with CLONE_PARENT
> is not allowed, but it is not specified how the exit_signal is to be set
> (or is set) when using the CLONE_PARENT flag.

Would you mind providing a small C program that demonstrates this?

> 
> Signed-off-by: Sargun Dhillon <sargun@sargun.me>
> ---
>  man2/clone.2 | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git a/man2/clone.2 b/man2/clone.2
> index 4c5b4ac6b..0b2a60482 100644
> --- a/man2/clone.2
> +++ b/man2/clone.2
> @@ -290,7 +290,13 @@ The termination signal is specified in the low byte of
>  .RB ( clone ())
>  or in
>  .I cl_args.exit_signal
> -.RB ( clone3 ()).
> +.RB ( clone3 ()),
> +unless
> +.BR CLONE_PARENT
> +flag is set. If the

Please use semantic newlines.  See man-pages(7).

$ MANWIDTH=72 man 7 man-pages | sed -n '/Use semantic newlines/,/^$/p';
   Use semantic newlines
     In the source of a manual page, new sentences should  be  started
     on new lines, long sentences should be split into lines at clause
     breaks  (commas, semicolons, colons, and so on), and long clauses
     should be split at phrase boundaries.  This convention, sometimes
     known as "semantic newlines", makes it easier to see  the  effect
     of  patches,  which often operate at the level of individual sen‐
     tences, clauses, or phrases.


Thanks,
Alex


> +.BR CLONE_PARENT
> +flag is set, then the exit_signal is copied from the calling process's process
> +group leader.
>  If this signal is specified as anything other than
>  .BR SIGCHLD ,
>  then the parent process must specify the

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


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