public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mzglcbz at 0pointer dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/31784] New: RFE: ability to control ambient caps in posix_spawn/pidfd_spawn Date: Wed, 22 May 2024 08:46:06 +0000 [thread overview] Message-ID: <bug-31784-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31784 Bug ID: 31784 Summary: RFE: ability to control ambient caps in posix_spawn/pidfd_spawn Product: glibc Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: mzglcbz at 0pointer dot net CC: drepper.fsp at gmail dot com Target Milestone: --- systemd uses pidfd_spawn/posix_spawn these days for process invocation. But there's one more thing we are missing: we want to pass ambient capabilities to invoked processes. This is a bit messy right now, because we have to raise the ambient caps *before* we invoke pidfd_spawn/posix_spawn where they will effect the original process, even if we really don't want that. We'd much rather have them only effect the invoked process, i.e. raise between the clone() + execev() in the child. Related to this: https://github.com/systemd/systemd/pull/32937 -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-05-22 8:46 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-22 8:46 mzglcbz at 0pointer dot net [this message] 2024-05-22 9:43 ` [Bug libc/31784] " fweimer at redhat dot com 2024-05-22 9:55 ` mzglcbz at 0pointer dot net 2024-05-22 16:00 ` stlman at poczta dot fm 2024-05-22 17:23 ` fweimer at redhat dot com 2024-05-22 21:12 ` mzglcbz at 0pointer dot net 2024-05-22 21:24 ` fweimer at redhat dot com 2024-05-23 12:31 ` adhemerval.zanella at linaro dot org 2024-05-23 13:52 ` mzglcbz at 0pointer dot net
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-31784-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).