public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/31784] RFE: ability to control ambient caps in posix_spawn/pidfd_spawn
Date: Thu, 23 May 2024 12:31:42 +0000	[thread overview]
Message-ID: <bug-31784-131-SVXSMtghE7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31784-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31784

Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adhemerval.zanella at linaro dot o
                   |                            |rg

--- Comment #6 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
There are projects like rsyscall [1], which essentially exposes clone as a
first-order interface and makes process creation a server-like interface where
the caller issues the syscall commands to be executed in the child.  This
allows for great flexibility (since it bypass libc for process creation), but
it is somewhat complex and I am not sure of the implication of trying to adjust
the idea for a libc-like interface.

Another approach is a fork-like interface (where you can add some flags to
define what is shared or to gate the clone flags) along with a callback.  It
has the issue of what kind of function the callback would be possible to run
(and historically users over-abused it to overcome its limitations).

[1] http://catern.com/rsys21.pdf

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-05-23 12:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22  8:46 [Bug libc/31784] New: " mzglcbz at 0pointer dot net
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 [this message]
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-SVXSMtghE7@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: 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).