From: "Serge E. Hallyn" <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
To: Aristeu Rozanski <aris-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
Serge Hallyn
<serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>,
"Eric W. Biederman"
<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Subject: Re: Getting userns enabled in vendor kernels
Date: Thu, 14 Nov 2013 17:48:32 +0000 [thread overview]
Message-ID: <20131114174832.GA14809@mail.hallyn.com> (raw)
In-Reply-To: <20131114174401.GF12097-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Quoting Aristeu Rozanski (aris-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org):
> (Replying also to Serge, same argument)
> On Thu, Nov 14, 2013 at 07:52:53AM -0800, James Bottomley wrote:
> > The thing that worries me is that turning this off means no-one will
> > work on the bugs and one day distros will start to use USER_NS for
> > things other than containers. When that happens, container roots will
> > need to use it to bring up distro IaaS instances.
>
> True, but the status we have now is that USER_NS is disabled completely
> in Fedora. This approach will split the process in two: enable part of
> it, let it soak, solve problems, enable user created namespaces later.
Right - so my suggestion is that we agree on a 100% identical patch for anyone
who must use such a patch to justify enabling USER_NS to use. But that we not
push it upstream. (Ubuntu would hopefully not use it - unless the overmount bug
does not get fixed in a timely manner.)
-serge
next prev parent reply other threads:[~2013-11-14 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 15:13 Getting userns enabled in vendor kernels Daniel P. Berrange
[not found] ` <20131113151330.GZ32643-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-11-13 16:30 ` Serge Hallyn
2013-11-14 15:52 ` James Bottomley
[not found] ` <1384444373.2005.8.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2013-11-14 17:44 ` Aristeu Rozanski
[not found] ` <20131114174401.GF12097-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-11-14 17:48 ` Serge E. Hallyn [this message]
2013-11-15 5:19 ` Gao feng
[not found] ` <5285AEF1.6000503-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-11-15 8:52 ` Eric W. Biederman
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=20131114174832.GA14809@mail.hallyn.com \
--to=serge-a9i7lubdfnhqt0dzr+alfa@public.gmane.org \
--cc=aris-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.