From: "Cristian Rodríguez" <cr@cristianrodriguez.net>
To: libc-alpha@sourceware.org
Subject: Re: [RFC] posix: Make system, popen, and wordexp try pidfd_spawn first (BZ 34001)
Date: Fri, 31 Jul 2026 14:08:12 -0400 [thread overview]
Message-ID: <CAPBLoAf43kmDBPxvkY_erV=Yppmd6oyuLJJDVb+HXfe=QaVi7A@mail.gmail.com> (raw)
In-Reply-To: <2adf9408-f1c3-40a4-b0d4-cd4f7cb2d502@linaro.org>
On Thu, Jul 30, 2026 at 1:58 PM Adhemerval Zanella Netto
<adhemerval.zanella@linaro.org> wrote:
> Ping, should we considere this for 2.45?
This will fix PID reuse bugs that are impossible to addressany other
way. Please consider including this fix in the next release.
prev parent reply other threads:[~2026-07-31 18:08 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
2026-07-30 17:58 ` Adhemerval Zanella Netto
2026-07-31 18:08 ` Cristian Rodríguez [this message]
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='CAPBLoAf43kmDBPxvkY_erV=Yppmd6oyuLJJDVb+HXfe=QaVi7A@mail.gmail.com' \
--to=cr@cristianrodriguez.net \
--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).