From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org,
"Cristian Rodríguez" <cr@cristianrodriguez.net>
Subject: Re: [RFC] posix: Make system, popen, and wordexp try pidfd_spawn first (BZ 34001)
Date: Mon, 4 May 2026 10:58:49 -0300 [thread overview]
Message-ID: <800c5588-44e7-40a3-b496-950147832f2a@linaro.org> (raw)
In-Reply-To: <lhuzf2fthc8.fsf@oldenburg.str.redhat.com>
On 04/05/26 10:49, Florian Weimer wrote:
> * Adhemerval Zanella:
>
>> This patch updates system, popen, and wordexp to use a new internal
>> process management abstraction (__spawn_process_create, __spawn_process_wait,
>> and __spawn_process_kill) that leverages pidfd_spawn on supported Linux
>> kernels before falling back to traditional posix_spawn.
>
> How does this change the way SIGCHLD is delivered?
It uses pidfd_spawn internally, which still uses '.exit_signal = SIGCHLD,'. We
can an internal-only interface to remove it, but I am not sure if this is really
required (afaik waitid (PIDFD, ...) will signal an error if the process is
already reaped).
And this lead to another question: should we omit SIGCHLD on pidfd_spawn?
next prev parent reply other threads:[~2026-05-04 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 20:00 Adhemerval Zanella
2026-05-04 13:49 ` Florian Weimer
2026-05-04 13:58 ` Adhemerval Zanella Netto [this message]
2026-05-05 13:05 ` Cristian Rodríguez
2026-05-05 13:07 ` Adhemerval Zanella Netto
2026-05-05 15:03 ` Florian Weimer
2026-05-05 15:20 ` Adhemerval Zanella Netto
2026-05-08 13:26 ` Cristian Rodriguez
2026-07-30 17:58 ` Adhemerval Zanella Netto
2026-07-31 18:08 ` Cristian Rodríguez
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=800c5588-44e7-40a3-b496-950147832f2a@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=cr@cristianrodriguez.net \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).