linux-kernel - Re: [RFC] Control Groups Roadmap ideas

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] [day] [month] [year] [list]

Message-ID: <6599ad830804140803p2a97c96mbc24f73e1a687aee@mail.gmail.com>
Date:	Mon, 14 Apr 2008 08:03:57 -0700
From:	"Paul Menage" <menage@...gle.com>
To:	"Serge E. Hallyn" <serue@...ibm.com>
Cc:	"Linux Containers" <containers@...ts.linux-foundation.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] Control Groups Roadmap ideas

On Mon, Apr 14, 2008 at 7:11 AM, Serge E. Hallyn <serue@...ibm.com> wrote:
>
>  then all tasks are mapped under /containers.  If login does a
>  clone(CLONE_NEWNS) for hallyn's login to give him a private /tmp,
>  then hallyn ends up under /containers/node_xyz, but we don't want him
>  to be virtualized under there.  So I assume we'd want a virt.lock file
>  or something like that so, that when I create a container, my
>  start_container script can echo 1 > /containers/node_abc/virt.lock

Yes, something like that.

>
>  I assume the container will also have to remount a fresh copy of the
>  cgroup composition so it can have the dentry for /containers/node_abc
>  as the root dentry for /containers?

Yes.

Paul
--
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/