public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: yo@cristianrodriguez.net,  libc-alpha@sourceware.org
Subject: Re: [RFC] posix: Make system, popen, and wordexp try pidfd_spawn first (BZ 34001)
Date: Tue, 05 May 2026 17:03:51 +0200	[thread overview]
Message-ID: <lhuecjpsxt4.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <3665a7b4-2af8-4207-ab69-bc9c4e8c496b@linaro.org> (Adhemerval Zanella Netto's message of "Tue, 5 May 2026 10:07:16 -0300")

* Adhemerval Zanella Netto:

> On 05/05/26 10:05, Cristian Rodríguez wrote:
>> On Mon, May 4, 2026 at 9:58 AM Adhemerval Zanella Netto
>> <adhemerval.zanella@linaro.org> wrote:
>>  (afaik waitid (PIDFD, ...) will signal an error if the process is
>>> already reaped).
>> 
>> Yes, it will return ECHILD..afaik.
>
> And I am not sure we can change it, because it will subtly change the
> functions semantics and we will always need a clone fallback (that
> always send the signal) for ABI that do not have clone3 and on kernel
> that do not support it.

I think we could perhaps hide the process launch for wordexp, but not
for system and popen.  For system and popen, some applications expect to
see signals.

Thanks,
Florian


  reply	other threads:[~2026-05-05 15:04 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
2026-05-05 13:05     ` Cristian Rodríguez
2026-05-05 13:07       ` Adhemerval Zanella Netto
2026-05-05 15:03         ` Florian Weimer [this message]
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=lhuecjpsxt4.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    --cc=yo@cristianrodriguez.net \
    /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).