public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Cristian Rodriguez <yo@cristianrodriguez.net>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [RFC] posix: Make system, popen, and wordexp try pidfd_spawn first (BZ 34001)
Date: Fri, 8 May 2026 09:26:07 -0400	[thread overview]
Message-ID: <CAPBLoAe5Dz1R+VwLPwrnaMyXu0Cpm+6G=+578k2prgV5q3==tQ@mail.gmail.com> (raw)
In-Reply-To: <3b78f30a-018a-472e-aa70-b22f02faa113@linaro.org>

On Tue, May 5, 2026 at 11:20 AM Adhemerval Zanella Netto
<adhemerval.zanella@linaro.org> wrote:
>
>
>
> On 05/05/26 12:03, Florian Weimer wrote:
> > * Adhemerval Zanella Netto:
> >

> But back to the main RFC, would this be an acceptable change?

It would be very nice if someone could ack this.
It resolves PID reuse problems that calling applications can't actually fix.
it is possible for example that system() or wordexp calls
`__kill_noerrno` on a PID that has already been reused if either
the system has a heavy process creation load or is only slightly
loaded and uses the default or low pid.max.

  reply	other threads:[~2026-05-08 13:26 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
2026-05-05 15:20           ` Adhemerval Zanella Netto
2026-05-08 13:26             ` Cristian Rodriguez [this message]
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='CAPBLoAe5Dz1R+VwLPwrnaMyXu0Cpm+6G=+578k2prgV5q3==tQ@mail.gmail.com' \
    --to=yo@cristianrodriguez.net \
    --cc=adhemerval.zanella@linaro.org \
    --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).