All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Max Kellermann <max.kellermann@ionos.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] man2/clone.2: clarify that CLONE_CLEAR_SIGHAND does not affect SIG_IGN
Date: Mon, 30 Oct 2023 14:47:46 +0100	[thread overview]
Message-ID: <ZT-0Aip9lh1ZoywW@debian> (raw)
In-Reply-To: <20231030125835.568711-1-max.kellermann@ionos.com>

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]

Hello Max,

On Mon, Oct 30, 2023 at 01:58:35PM +0100, Max Kellermann wrote:
> The old wording was ambiguous, but it is important to know that
> signals that were set to SIG_IGN will not be restored to SIG_DFL.
> 
> Signed-off-by: Max Kellermann <max.kellermann@ionos.com>

Would you mind sending an example program that proves this?

Thanks,
Alex

> ---
>  man2/clone.2 | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/man2/clone.2 b/man2/clone.2
> index 4a75b557b..deb4bdb5b 100644
> --- a/man2/clone.2
> +++ b/man2/clone.2
> @@ -455,7 +455,8 @@ flag is also employed.)
>  By default, signal dispositions in the child thread are the same as
>  in the parent.
>  If this flag is specified,
> -then all signals that are handled in the parent
> +then all signals that are handled in the parent (and not set to
> +.BR SIG_IGN )
>  are reset to their default dispositions
>  .RB ( SIG_DFL )
>  in the child.
> -- 
> 2.39.2
> 

-- 
<https://www.alejandro-colomar.es/>

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

  reply	other threads:[~2023-10-30 13:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 12:58 [PATCH] man2/clone.2: clarify that CLONE_CLEAR_SIGHAND does not affect SIG_IGN Max Kellermann
2023-10-30 13:47 ` Alejandro Colomar [this message]
2023-10-30 13:52   ` Max Kellermann
2023-10-30 16:21     ` Alejandro Colomar
2023-10-30 16:27       ` [PATCH v2] " Max Kellermann
2023-10-31 12:45         ` Alejandro Colomar

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=ZT-0Aip9lh1ZoywW@debian \
    --to=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=max.kellermann@ionos.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 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.