From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Daniel Lezcano <daniel.lezcano-GANU6spQydw@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
Paul Menage <menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
"Eric W. Biederman"
<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Subject: Re: [patch 2/2] Remove the ns_cgroup
Date: Mon, 28 Dec 2009 17:36:11 -0600 [thread overview]
Message-ID: <20091228233611.GA6309@us.ibm.com> (raw)
In-Reply-To: <20091228230623.907397717-7Ha4D/yM3XKqUVqbrEjtMkN0fxke0PB7qyM6JfAXOaQ@public.gmane.org>
Quoting Daniel Lezcano (daniel.lezcano-GANU6spQydw@public.gmane.org):
> The ns_cgroup is an annoying cgroup at the namespace / cgroup frontier.
True. However, it remains - apart from using smack or SELinux - the
only way to truly lock a container into a cgroup configuration. That's
unlikely to change until we finally support user namespaces in the VFS.
Do we worry about that?
-serge
next prev parent reply other threads:[~2009-12-28 23:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 23:04 [patch 0/2] Remove the ns_cgroup Daniel Lezcano
2009-12-28 23:04 ` [patch 1/2] Add clone_child control file Daniel Lezcano
[not found] ` <20091228230620.494084022-7Ha4D/yM3XKqUVqbrEjtMkN0fxke0PB7qyM6JfAXOaQ@public.gmane.org>
2010-01-07 1:28 ` Paul Menage
[not found] ` <6599ad831001061728n63375ff8qb3a084e3f9fd7c98-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-08 12:59 ` Daniel Lezcano
2009-12-28 23:04 ` [patch 2/2] Remove the ns_cgroup Daniel Lezcano
[not found] ` <20091228230623.907397717-7Ha4D/yM3XKqUVqbrEjtMkN0fxke0PB7qyM6JfAXOaQ@public.gmane.org>
2009-12-28 23:36 ` Serge E. Hallyn [this message]
[not found] ` <20091228233611.GA6309-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-01-07 0:38 ` Paul Menage
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091228233611.GA6309@us.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=daniel.lezcano-GANU6spQydw@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox