From: Florian Weimer <fweimer@redhat.com>
To: Luca Boccassi <bluca@debian.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v8 0/7] Add pidfd and cgroupv2 support for process creation
Date: Mon, 28 Aug 2023 15:21:28 +0200 [thread overview]
Message-ID: <875y4zuwtj.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <a63c53f221eb68d9e7153fe2679763d3d4f667d0.camel@debian.org> (Luca Boccassi's message of "Mon, 28 Aug 2023 13:52:42 +0100")
* Luca Boccassi:
> These are real race conditions, that cannot be solved otherwise,
> characterizing them as 'programming errors' is very misleading and
> wrong.
>
> We very much need both of those interfaces in systemd, and fully intend
> to use them as soon as they are available. We are slowly moving towards
> using pidfds everywhere to be able to do end-to-end race-free process
> tracking and management, and these are fundamental pieces for this
> effort. From what I can read the GNOME developers feel the same way,
> and I wouldn't be surprised if QT followed suit too given what you
> mentioned in the cover letter.
>
> Surely implementing useful, core functionality for the direct and
> immediate benefit of 3 major Linux projects is a reason as solid as you
> could ever find to add a new interface.
I see value in adding fork support, too.
The fundamental issue with the fork part is that it's not future-proof
at all. The programming model is completely different from the kernel
interface.
If I start a discussion about API alternatives, who should I Cc: except
you and Rich?
Thanks,
Florian
next prev parent reply other threads:[~2023-08-28 13:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 14:06 Adhemerval Zanella
2023-08-18 14:06 ` [PATCH v8 1/7] arm: Add the clone3 wrapper Adhemerval Zanella
2023-08-18 14:06 ` [PATCH v8 2/7] mips: " Adhemerval Zanella
2023-08-18 14:06 ` [PATCH v8 3/7] linux: Define __ASSUME_CLONE3 to 0 for alpha, ia64, nios2, sh, and sparc Adhemerval Zanella
2023-08-24 6:06 ` Florian Weimer
2023-08-18 14:06 ` [PATCH v8 4/7] linux: Add posix_spawnattr_{get,set}cgroup_np (BZ 26731) Adhemerval Zanella
2023-08-24 7:00 ` Florian Weimer
2023-08-18 14:06 ` [PATCH v8 5/7] posix: Add pidfd_spawn and pidfd_spawnp (BZ 30349) Adhemerval Zanella
2023-08-24 7:13 ` Florian Weimer
2023-08-24 15:43 ` Adhemerval Zanella Netto
2023-08-24 17:00 ` Florian Weimer
2023-08-24 17:10 ` Adhemerval Zanella Netto
2023-08-24 18:18 ` Florian Weimer
2023-08-24 18:22 ` Adhemerval Zanella Netto
2023-08-25 10:38 ` Florian Weimer
2023-08-25 16:37 ` Adhemerval Zanella Netto
2023-08-18 14:06 ` [PATCH v8 6/7] posix: Add fork_np (BZ 26371) Adhemerval Zanella
2023-08-24 6:07 ` Florian Weimer
2023-08-18 14:06 ` [PATCH v8 7/7] linux: Add pidfd_getpid Adhemerval Zanella
2023-08-24 7:53 ` Florian Weimer
2023-08-18 17:51 ` [PATCH v8 0/7] Add pidfd and cgroupv2 support for process creation Rich Felker
2023-08-18 18:34 ` Adhemerval Zanella Netto
2023-08-28 12:52 ` Luca Boccassi
2023-08-28 13:21 ` Florian Weimer [this message]
2023-08-28 13:50 ` Luca Boccassi
2023-08-21 6:53 ` Florian Weimer
2023-08-21 13:55 ` Rich Felker
2023-08-24 7:25 ` Florian Weimer
2023-08-24 12:21 ` Rich Felker
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=875y4zuwtj.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=bluca@debian.org \
--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).