[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160226224727.GB24680@ubuntumail>
Date: Fri, 26 Feb 2016 22:47:27 +0000
From: Serge Hallyn <serge.hallyn@...ntu.com>
To: Alban Crequy <alban.crequy@...il.com>
Cc: LXC development mailing-list
<lxc-devel@...ts.linuxcontainers.org>,
Linux API <linux-api@...r.kernel.org>,
Linux Containers <containers@...ts.linux-foundation.org>,
Johannes Weiner <hannes@...xchg.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
gregkh@...uxfoundation.org, Tejun Heo <tj@...nel.org>,
cgroups@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [lxc-devel] CGroup Namespaces (v10)
Quoting Alban Crequy (alban.crequy@...il.com):
> Hi,
>
> On 29 January 2016 at 09:54, <serge.hallyn@...ntu.com> wrote:
> > Hi,
> >
> > following is a revised set of the CGroup Namespace patchset which Aditya
> > Kali has previously sent. The code can also be found in the cgroupns.v10
> > branch of
> >
> > https://git.kernel.org/cgit/linux/kernel/git/sergeh/linux-security.git/
> >
> > To summarize the semantics:
> >
> > 1. CLONE_NEWCGROUP re-uses 0x02000000, which was previously CLONE_STOPPED
>
> What's the best way for a userspace application to test at run-time
> whether the kernel supports cgroup namespaces? Would you recommend to
> test if the file /proc/self/ns/cgroup exists?
Yup.
Powered by blists - more mailing lists