From: Aristeu Rozanski <aris@redhat.com>
To: linux-kernel@vger.kernel.org, cgroups@vger.kernel.org
Cc: Tejun Heo <tj@kernel.org>, Li Zefan <lizefan@huawei.com>,
Hillf Danton <dhillf@gmail.com>,
Lennart Poettering <lpoetter@redhat.com>,
Hugh Dickins <hughd@google.com>
Subject: [PATCH v2 1/2] cgroups: add documentation on extended attributes usage
Date: Tue, 11 Sep 2012 16:28:10 -0400 [thread overview]
Message-ID: <20120911202810.406133423@napanee.usersys.redhat.com> (raw)
In-Reply-To: <20120911202809.988739953@napanee.usersys.redhat.com>
[-- Attachment #1: doc.patch --]
[-- Type: text/plain, Size: 1887 bytes --]
v2: update cgroups.txt instead of creating a new file
Cc: Li Zefan <lizefan@huawei.com>
Cc: Tejun Heo <tj@kernel.org>
Cc: Hugh Dickins <hughd@google.com>
Cc: Hillf Danton <dhillf@gmail.com>
Cc: Lennart Poettering <lpoetter@redhat.com>
Signed-off-by: Aristeu Rozanski <aris@redhat.com>
---
Documentation/cgroups/cgroups.txt | 24 ++++++++++++++++++++++--
1 file changed, 22 insertions(+), 2 deletions(-)
Index: github/Documentation/cgroups/cgroups.txt
===================================================================
--- github.orig/Documentation/cgroups/cgroups.txt 2012-08-16 10:24:48.437596817 -0400
+++ github/Documentation/cgroups/cgroups.txt 2012-09-07 10:23:19.974357952 -0400
@@ -29,7 +29,8 @@
3.1 Overview
3.2 Synchronization
3.3 Subsystem API
-4. Questions
+4. Extended attributes usage
+5. Questions
1. Control Groups
=================
@@ -650,7 +651,26 @@
the default hierarchy (which never has sub-cgroups) and a hierarchy
that is being created/destroyed (and hence has no sub-cgroups).
-4. Questions
+4. Extended attribute usage
+===========================
+
+cgroup filesystem supports certain types of extended attributes in its
+directories and files. The current supported types are:
+ - Trusted (XATTR_TRUSTED)
+ - Security (XATTR_SECURITY)
+
+Both require CAP_SYS_ADMIN capability to set.
+
+Like in tmpfs, the extended attributes in cgroup filesystem are stored
+using kernel memory and it's advised to keep the usage at minimum. This
+is the reason why user defined extended attributes are not supported, since
+any user can do it and there's no limit in the value size.
+
+The current known users for this feature are SELinux to limit cgroup usage
+in containers and systemd for assorted meta data like main PID in a cgroup
+(systemd creates a cgroup per service).
+
+5. Questions
============
Q: what's up with this '/bin/echo' ?
next prev parent reply other threads:[~2012-09-11 20:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 20:28 [PATCH v2 0/2] cgroups: add documentation on extended attributes and simple_xattr functions Aristeu Rozanski
2012-09-11 20:28 ` Aristeu Rozanski [this message]
2012-09-12 1:26 ` [PATCH v2 1/2] cgroups: add documentation on extended attributes usage Li Zefan
2012-09-11 20:28 ` [PATCH v2 2/2] fs: add missing documentation to simple_xattr functions Aristeu Rozanski
2012-09-13 18:02 ` Randy Dunlap
2012-09-13 18:11 ` Tejun Heo
2012-09-13 18:23 ` Aristeu Rozanski
2012-09-11 21:31 ` [PATCH v2 0/2] cgroups: add documentation on extended attributes and " Tejun Heo
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=20120911202810.406133423@napanee.usersys.redhat.com \
--to=aris@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=dhillf@gmail.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=lpoetter@redhat.com \
--cc=tj@kernel.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
all inboxes | Powered by JetHome®