From: ebiederm@xmission.com (Eric W. Biederman)
To: Kenton Varda <kenton@sandstorm.io>
Cc: Alexander Larsson <alexl@redhat.com>,
gnome-os-list@gnome.org,
Linux Containers <containers@lists.linux-foundation.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
mclasen@redhat.com,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] devpts: Add ptmx_uid and ptmx_gid options
Date: Thu, 28 May 2015 16:50:37 -0500 [thread overview]
Message-ID: <87oal4e5hu.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <CAOP=4wggpXOC4qLWgNAdw7Ws4vtYR=hscNYzDCfby+-VUxhoQg@mail.gmail.com> (Kenton Varda's message of "Thu, 28 May 2015 13:17:30 -0700")
Kenton Varda <kenton@sandstorm.io> writes:
> On Thu, May 28, 2015 at 1:06 PM, Alexander Larsson <alexl@redhat.com> wrote:
>> On Thu, 2015-05-28 at 12:14 -0500, Eric W. Biederman wrote:
>>>
>>> > Where does the second namespace enter into this?
>>>
>>> Step a. Create create a user namespace where uid 0 is mapped to your
>>> real uid, and set up your sandbox (aka mount /dev/pts and everything
>>> else).
>>>
>>> Step b. Create a nested user namespace where your uid is identity
>>> mapped and run your desktop application. You can even drop all caps
>>> in
>>> your namespace.
>>
>> Just tried this. Its not the nicest, and it doubles the number of
>> namespaces in action for each sandbox, but it does work.
>
> How much overhead is involved in each user namespace?
sizeof(struct user_namespace).
> Is there any system-wide limit on total namespaces, other than RAM?
There is a system-wide maximum depth, but not count.
> Is there
> (non-negligible) CPU overhead for each syscall seeking permissions in
> the namespace?
ns_capable(ns, X) in some cases can walk up the from a starting user
namespace to the initial user. (The only non-constant operation I am
aware of). However unless the user namespace depth is deep it should
still take a negligible amount of time.
Eric
next prev parent reply other threads:[~2015-05-28 21:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 1:04 Andy Lutomirski
2015-03-26 19:29 ` Andy Lutomirski
2015-03-27 9:03 ` James Bottomley
2015-03-31 7:57 ` Alexander Larsson
2015-03-31 13:06 ` Andy Lutomirski
2015-03-31 13:07 ` James Bottomley
2015-03-31 13:11 ` Alexander Larsson
2015-03-31 13:12 ` Andy Lutomirski
2015-03-31 13:23 ` James Bottomley
2015-03-31 13:44 ` Andy Lutomirski
2015-03-31 13:55 ` James Bottomley
2015-03-31 13:59 ` Andy Lutomirski
2015-03-31 14:08 ` James Bottomley
2015-03-31 14:17 ` Alexander Larsson
2015-04-02 10:12 ` James Bottomley
2015-04-02 14:06 ` Andy Lutomirski
2015-04-02 14:29 ` Alexander Larsson
2015-04-02 14:33 ` Andy Lutomirski
2015-04-02 15:49 ` Serge Hallyn
2015-04-02 18:27 ` Eric W. Biederman
2015-05-27 21:32 ` Andy Lutomirski
2015-05-28 16:44 ` Eric W. Biederman
2015-05-28 17:01 ` Alexander Larsson
2015-05-28 17:14 ` Eric W. Biederman
2015-05-28 17:35 ` Alexander Larsson
2015-05-28 20:06 ` Alexander Larsson
2015-05-28 20:17 ` Kenton Varda
2015-05-28 21:50 ` Eric W. Biederman [this message]
2015-05-28 17:30 ` Andy Lutomirski
2015-05-28 19:42 ` Eric W. Biederman
2016-03-08 4:59 ` Andy Lutomirski
2016-03-08 9:16 ` Alexander Larsson
2016-03-08 18:17 ` Andy Lutomirski
2015-05-18 21:04 ` Alexander Larsson
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=87oal4e5hu.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=alexl@redhat.com \
--cc=containers@lists.linux-foundation.org \
--cc=gnome-os-list@gnome.org \
--cc=kenton@sandstorm.io \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mclasen@redhat.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
Powered by JetHome