From: "John Ericson" <list@johnericson.me>
To: "Christian Brauner" <christian.brauner@ubuntu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"David Laight" <David.Laight@ACULAB.COM>,
"Andy Lutomirski" <luto@kernel.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
"Kernel Hardening" <kernel-hardening@lists.openwall.com>,
"Jann Horn" <jann@thejh.net>,
"Christian Brauner" <christian.brauner@canonical.com>
Subject: Re: Leveraging pidfs for process creation without fork
Date: Thu, 29 Jul 2021 10:54:08 -0400 [thread overview]
Message-ID: <e048b871-55db-4e7f-96c9-40aabdd076c5@www.fastmail.com> (raw)
In-Reply-To: <20210729142415.qovpzky537zkg3dp@wittgenstein>
Wonderful, looking forward to it reading it then!
John
On Thu, Jul 29, 2021, at 10:24 AM, Christian Brauner wrote:
> On Wed, Jul 28, 2021 at 12:37:57PM -0400, John Cotton Ericson wrote:
> > Hi,
> >
> > I was excited to learn about about pidfds the other day, precisely in hopes
> > that it would open the door to such a "sane process creation API". I
> > searched the LKML, found this thread, and now hope to rekindle the
> > discussion; my apologies if there has been more discussion since that I
>
> Yeah, I haven't forgotten this discussion. A proposal is on my todo list
> for this year. So far I've scheduled some time to work on this in the
> fall.
>
> Thanks!
> Christian
next prev parent reply other threads:[~2021-07-29 14:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 17:47 forkat(int pidfd), execveat(int pidfd), other awful things? Jason A. Donenfeld
2021-02-01 17:51 ` Jason A. Donenfeld
2021-02-01 18:20 ` Christian Brauner
2021-02-01 18:29 ` Andy Lutomirski
2021-02-02 9:23 ` David Laight
2021-07-28 16:37 ` Leveraging pidfs for process creation without fork John Cotton Ericson
2021-07-29 14:24 ` Christian Brauner
2021-07-29 14:54 ` John Ericson [this message]
2021-07-30 1:41 ` Al Viro
[not found] ` <1468d75c-57ae-42aa-85ce-2bee8d403763@www.fastmail.com>
2021-07-31 22:42 ` Al Viro
2021-08-02 12:19 ` Christian Brauner
2021-08-03 6:00 ` John Cotton Ericson
2021-02-01 18:32 ` forkat(int pidfd), execveat(int pidfd), other awful things? Casey Schaufler
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=e048b871-55db-4e7f-96c9-40aabdd076c5@www.fastmail.com \
--to=list@johnericson.me \
--cc=David.Laight@ACULAB.COM \
--cc=Jason@zx2c4.com \
--cc=christian.brauner@canonical.com \
--cc=christian.brauner@ubuntu.com \
--cc=jann@thejh.net \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.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 NNTP newsgroup(s).