From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org, Szabolcs Nagy <szabolcs.nagy@arm.com>,
"H . J . Lu" <hjl.tools@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>
Subject: [PATCH v2 01/11] linux: Do not reset signal handler in posix_spawn if it is already SIG_DFL
Date: Fri, 4 Nov 2022 16:01:02 -0300 [thread overview]
Message-ID: <20221104190112.2566409-2-adhemerval.zanella@linaro.org> (raw)
In-Reply-To: <20221104190112.2566409-1-adhemerval.zanella@linaro.org>
There is no need to issue another sigaction is the disposition is
already SIG_DFL.
Checked on x86_64-linux-gnu.
---
sysdeps/unix/sysv/linux/spawni.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sysdeps/unix/sysv/linux/spawni.c b/sysdeps/unix/sysv/linux/spawni.c
index ee843a2247..65ee03c804 100644
--- a/sysdeps/unix/sysv/linux/spawni.c
+++ b/sysdeps/unix/sysv/linux/spawni.c
@@ -129,7 +129,7 @@ __spawni_child (void *arguments)
else
{
__libc_sigaction (sig, 0, &sa);
- if (sa.sa_handler == SIG_IGN)
+ if (sa.sa_handler == SIG_IGN || sa.sa_handler == SIG_DFL)
continue;
sa.sa_handler = SIG_DFL;
}
--
2.34.1
next prev parent reply other threads:[~2022-11-04 19:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 19:01 [PATCH v2 00/11] Optimize posix_spawn signal setup with clone3 Adhemerval Zanella
2022-11-04 19:01 ` Adhemerval Zanella [this message]
2023-01-11 21:27 ` [PATCH v2 01/11] linux: Do not reset signal handler in posix_spawn if it is already SIG_DFL Carlos O'Donell
2022-11-04 19:01 ` [PATCH v2 02/11] linux: Extend internal clone3 documentation Adhemerval Zanella
2022-11-07 16:40 ` Szabolcs Nagy
2023-01-11 21:35 ` Carlos O'Donell
2022-11-04 19:01 ` [PATCH v2 03/11] Linux: Do not align the stack for __clone3 Adhemerval Zanella
2023-01-11 21:43 ` Carlos O'Donell
2022-11-04 19:01 ` [PATCH v2 04/11] linux: Add clone3 CLONE_CLEAR_SIGHAND optimization to posix_spawn Adhemerval Zanella
2023-01-11 21:44 ` Carlos O'Donell
2022-11-04 19:01 ` [PATCH v2 05/11] powerpc64: Add the clone3 wrapper Adhemerval Zanella
2022-11-28 16:38 ` Paul E Murphy
2022-11-29 20:43 ` Adhemerval Zanella Netto
2022-11-04 19:01 ` [PATCH v2 06/11] aarch64: " Adhemerval Zanella
2022-11-07 16:14 ` Szabolcs Nagy
2022-11-04 19:01 ` [PATCH v2 07/11] s390x: " Adhemerval Zanella
2022-11-04 19:01 ` [PATCH v2 08/11] riscv: " Adhemerval Zanella
2022-11-04 19:01 ` [PATCH v2 09/11] arm: " Adhemerval Zanella
2022-11-04 19:01 ` [PATCH v2 10/11] mips: " Adhemerval Zanella
2022-11-04 19:01 ` [PATCH v2 11/11] Linux: optimize clone3 internal usage Adhemerval Zanella
2023-01-11 21:45 ` Carlos O'Donell
2023-01-11 21:24 ` [PATCH v2 00/11] Optimize posix_spawn signal setup with clone3 Carlos O'Donell
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=20221104190112.2566409-2-adhemerval.zanella@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=brauner@kernel.org \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=szabolcs.nagy@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).