public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bugzilla at tecnocode dot co.uk" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/30349] New: Support returning a pidfd from posix_spawn() Date: Thu, 13 Apr 2023 19:36:27 +0000 [thread overview] Message-ID: <bug-30349-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30349 Bug ID: 30349 Summary: Support returning a pidfd from posix_spawn() Product: glibc Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: bugzilla at tecnocode dot co.uk CC: drepper.fsp at gmail dot com Target Milestone: --- pidfd allows a process to keep a race-free handle to a child process, avoiding the problem of PID recycling meaning that a pid_t no longer refers to the process you thought it did. We’d like to be able to use pidfds in GLib for race-free signalling of subprocesses. GLib currently uses posix_spawn() to spawn those subprocesses, though, and it cannot return a pidfd. Could glibc please add a variant of posix_spawn() which returns a pidfd to the caller? I don’t know of the best API for this, but it could either be a new posix_spawn_with_pidfd() function, or be the existing posix_spawn() but somehow return a pidfd via a posix_spawnattr_t. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-04-13 19:36 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-13 19:36 bugzilla at tecnocode dot co.uk [this message] 2023-04-13 19:36 ` [Bug libc/30349] " bugzilla at tecnocode dot co.uk 2023-04-13 19:37 ` bugzilla at tecnocode dot co.uk 2023-04-13 20:16 ` adhemerval.zanella at linaro dot org 2023-04-13 21:00 ` adhemerval.zanella at linaro dot org 2023-04-14 13:25 ` adhemerval.zanella at linaro dot org 2023-04-14 15:00 ` adhemerval.zanella at linaro dot org 2023-04-14 15:02 ` adhemerval.zanella at linaro dot org 2023-04-18 17:59 ` adhemerval.zanella at linaro dot org 2023-04-18 21:38 ` adhemerval.zanella at linaro dot org 2023-05-15 17:01 ` bugzilla at tecnocode dot co.uk 2023-08-28 12:22 ` bluca at debian dot org 2023-09-05 16:10 ` adhemerval.zanella at linaro dot org 2023-09-05 16:17 ` bugzilla at tecnocode dot co.uk
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=bug-30349-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).