[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87r3jnfyx7.fsf@x220.int.ebiederm.org>
Date: Wed, 18 Nov 2015 03:18:44 -0600
From: ebiederm@...ssion.com (Eric W. Biederman)
To: "Serge E. Hallyn" <serge@...lyn.com>
Cc: Richard Weinberger <richard@....at>,
Richard Weinberger <richard.weinberger@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
"open list\:ABI\/API" <linux-api@...r.kernel.org>,
Linux Containers <containers@...ts.linux-foundation.org>,
LXC development mailing-list
<lxc-devel@...ts.linuxcontainers.org>, Tejun Heo <tj@...nel.org>,
cgroups mailinglist <cgroups@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: CGroup Namespaces (v4)
"Serge E. Hallyn" <serge@...lyn.com> writes:
> On Mon, Nov 16, 2015 at 04:24:27PM -0600, Eric W. Biederman wrote:
>> Similary have you considered what it required to be able to safely set
>> FS_USERNS_MOUNT?
>
> I pushed the one patch which I feel is needed to my branch (it's also
> included in another reply). Aditya had already added FS_USERNS_MOUNT to
> the cgroup fs flags, so I think we're now all set. I can start
> unprivileged containers which mount cgroupfs (which make systemd happy).
In principle that sounds very good, and I am glad to see that.
Let's hold off on merging the unprivileged part until everything else is
reviewed and merged and we have performed an extra hard look at the
security implications as it can be easy to overlook something when
relaxing the permissions.
Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists