From: Giuseppe Scrivano <gscrivan@redhat.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: Snaipe <snaipe@arista.com>,
alexander@mihalicyn.com, christian.brauner@ubuntu.com,
Linux Containers <containers@lists.linux.dev>,
cyphar@cyphar.com, ebiederm@xmission.com, geofft@ldpreload.com,
jcsible@cert.org, josh@joshtriplett.org, keescook@chromium.org,
linux-kernel@vger.kernel.org, luto@amacapital.net,
mic@digikod.net, mpatel@redhat.com, ptikhomirov@virtuozzo.com,
sargun@sargun.me, stgraber@ubuntu.com, vgoyal@redhat.com,
watl@google.com
Subject: Re: LPC 2020 Hackroom Session: summary and next steps for isolated user namespaces
Date: Mon, 10 May 2021 15:57:09 +0200 [thread overview]
Message-ID: <874kfahetm.fsf@redhat.com> (raw)
In-Reply-To: <87cztyhhc4.fsf@redhat.com> (Giuseppe Scrivano's message of "Mon, 10 May 2021 15:02:51 +0200")
Giuseppe Scrivano <gscrivan@redhat.com> writes:
>>> Any comments on this approach? Could we move forward with it?
>>
>> Can you send these to lkml? I'll have to go back through our previous
>> discussions, but offhand this looks good to me.
>
> I've just sent them to lkml.
and I've realized I forgot to CC containers@lists.linux.dev.
For anyone interested, the patches are here:
https://lore.kernel.org/lkml/20210510130011.1441834-1-gscrivan@redhat.com/T/#t
Regards,
Giuseppe
next prev parent reply other threads:[~2021-05-10 13:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 14:39 LPC 2020 Hackroom Session: summary and next steps for isolated user namespaces Christian Brauner
2020-10-10 4:26 ` Serge E. Hallyn
2020-10-11 20:53 ` Josh Triplett
2020-10-12 0:38 ` Andy Lutomirski
2020-10-12 5:01 ` Eric W. Biederman
2020-10-12 15:00 ` Serge E. Hallyn
2020-10-14 19:46 ` Eric W. Biederman
2020-10-15 14:27 ` Serge E. Hallyn
2020-10-17 15:04 ` Eric W. Biederman
2020-10-12 17:05 ` Giuseppe Scrivano
2020-10-13 12:46 ` Serge E. Hallyn
2020-10-13 15:17 ` Giuseppe Scrivano
2020-10-15 14:32 ` Serge E. Hallyn
2020-10-19 12:12 ` Giuseppe Scrivano
2021-04-21 17:27 ` Snaipe via Containers
2021-04-22 9:18 ` Giuseppe Scrivano
2021-04-23 14:36 ` Franklin “Snaipe” Mathieu via Containers
[not found] ` <20210507133703.GB22450@mail.hallyn.com>
2021-05-10 13:02 ` Giuseppe Scrivano
2021-05-10 13:57 ` Giuseppe Scrivano [this message]
2020-10-15 15:31 ` Enrico Weigelt, metux IT consult
2020-10-17 16:51 ` Eric W. Biederman
2020-10-18 10:20 ` Christian Brauner
[not found] ` <87h7qradml.fsf_-_@x220.int.ebiederm.org>
2020-10-19 0:15 ` The problem of setgroups and containers Eric W. Biederman
2020-10-19 20:07 ` [RFC][PATCH] userns: Limit process in a user namespace to what the creator is allowed Eric W. Biederman
2020-10-20 14:11 ` Christian Brauner
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=874kfahetm.fsf@redhat.com \
--to=gscrivan@redhat.com \
--cc=alexander@mihalicyn.com \
--cc=christian.brauner@ubuntu.com \
--cc=containers@lists.linux.dev \
--cc=cyphar@cyphar.com \
--cc=ebiederm@xmission.com \
--cc=geofft@ldpreload.com \
--cc=jcsible@cert.org \
--cc=josh@joshtriplett.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mic@digikod.net \
--cc=mpatel@redhat.com \
--cc=ptikhomirov@virtuozzo.com \
--cc=sargun@sargun.me \
--cc=serge@hallyn.com \
--cc=snaipe@arista.com \
--cc=stgraber@ubuntu.com \
--cc=vgoyal@redhat.com \
--cc=watl@google.com \
/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).