From: ebiederm@xmission.com (Eric W. Biederman)
To: "Michael Kerrisk \(man-pages\)" <mtk.manpages@gmail.com>
Cc: Linux Containers <containers@lists.linux-foundation.org>,
<linux-kernel@vger.kernel.org>
Subject: User namespaces and the memory control group
Date: Fri, 25 Jan 2013 01:59:05 -0800 [thread overview]
Message-ID: <87ip6llh1y.fsf@xmission.com> (raw)
For anyone who cares about resource control setting up the memory
control group in combination with user namespaces is strongly
recommended.
User namespaces are a particular problem when it comes to resource
control. Not all of the resources you can create with a user namespace
currently have ordinary resource limits. When you can switch uids
the ordinary resource limits don't mean much.
The memory control group is capable of limiting all of those things
today. So if you care about keeping rude users of your system under
control and you enable user namespaces setting up memory control groups
is to limit them is strongly recommended.
Eric
reply other threads:[~2013-01-25 9:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87ip6llh1y.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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