public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Max Kellermann <max.kellermann@ionos.com>
To: alx@kernel.org
Cc: linux-man@vger.kernel.org, Max Kellermann <max.kellermann@ionos.com>
Subject: [PATCH v2] man2/clone.2: clarify that CLONE_CLEAR_SIGHAND does not affect SIG_IGN
Date: Mon, 30 Oct 2023 17:27:33 +0100	[thread overview]
Message-ID: <20231030162733.598572-1-max.kellermann@ionos.com> (raw)
In-Reply-To: <ZT_YHozq7Pu_t9Nq@debian>

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.

This behavior was documented in the kernel commit that introduced the
feature:

 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b612e5df4587c934bd056bf05f4a1deca4de4f75

Signed-off-by: Max Kellermann <max.kellermann@ionos.com>
---
v1 -> v2: added link to kernel commit
---
 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


  reply	other threads:[~2023-10-30 16:27 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
2023-10-30 13:52   ` Max Kellermann
2023-10-30 16:21     ` Alejandro Colomar
2023-10-30 16:27       ` Max Kellermann [this message]
2023-10-31 12:45         ` [PATCH v2] " 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=20231030162733.598572-1-max.kellermann@ionos.com \
    --to=max.kellermann@ionos.com \
    --cc=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    /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