linux-kernel - Re: [lxc-devel] CGroup Namespaces (v10)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMXgnP4Wss0ctx7mHzD0WHL4+-fC59iLZNkYONE5pAeHYr18+A@mail.gmail.com>
Date:	Fri, 26 Feb 2016 14:18:23 +0100
From:	Alban Crequy <alban.crequy@...il.com>
To:	LXC development mailing-list <lxc-devel@...ts.linuxcontainers.org>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Aditya Kali <adityakali@...gle.com>,
	Linux API <linux-api@...r.kernel.org>,
	Linux Containers <containers@...ts.linux-foundation.org>,
	Johannes Weiner <hannes@...xchg.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)

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?

Thanks!
Alban