[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151117035458.GA3158@mail.hallyn.com>
Date: Mon, 16 Nov 2015 21:54:58 -0600
From: "Serge E. Hallyn" <serge@...lyn.com>
To: "Serge E. Hallyn" <serge@...lyn.com>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
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)
On Mon, Nov 16, 2015 at 07:40:26PM -0600, Serge E. Hallyn wrote:
> On Mon, Nov 16, 2015 at 07:13:49PM -0600, Serge E. Hallyn wrote:
> > 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 think the only thing we need to do is
> >
> > 1. go through and make sure that any ability to change mount flags is under
> > capable() (which I have not yet done). The cgroup_mount() itself checks that
> > flags are not changed, but there may be some subtle way to effect a change
> > that I'm not aware of yet.
> >
>
> At least the ability to change the clone_children and release agent through
> remount need to be restricted to init_user_ns root.
No, they can only be changed on a new mount, so these are fine.
--
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