From: Li Zefan <lizf@cn.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"containers@lists.linux-foundation.org"
<containers@lists.linux-foundation.org>,
"menage@google.com" <menage@google.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/2] cgroup allow subsys to set default mode of its own file
Date: Wed, 25 Feb 2009 16:01:13 +0800 [thread overview]
Message-ID: <49A4FAC9.2080701@cn.fujitsu.com> (raw)
In-Reply-To: <20090225163555.d2a0b24c.kamezawa.hiroyu@jp.fujitsu.com>
KAMEZAWA Hiroyuki wrote:
> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>
> cgroup's subsys has "readonly" files, but default permission is always
> rw-r--r--. This allows to create r--r--r-- file to subsys.
> (The user can do chmod on this read-only file. But this behavior is not
> different from current pseudo file systems as /proc.)
>
> Reason:
> When I wrote tools for maintain cgroup, I can't find which file is
> writable intarfece or not via cgroup file systems. (finally, I did
> dirty approach.)
> IMHO, showing "this file is read-only" in explicit way is useful
> for user-land (tools). In other story, a file whose name sounds read-only
> may have "trigger" operation and support reseting. In this case,
> "writable" is informative.
>
I once planed to do so. I think there's one trial issue, that some files are
read-only in top-cgroup, but read-write in sub-dirs, like cpuset.cpus and
cpuset.mems. But for those files, they must have a write function, so I think
it's still valid to mask them as read-write even they are in top-cgroup.
Unless Paul has different option towards this:
Acked-by: Li Zefan <lizf@cn.fujitsu.cn>
>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> ---
> include/linux/cgroup.h | 2 ++
> kernel/cgroup.c | 5 ++++-
> 2 files changed, 6 insertions(+), 1 deletion(-)
>
> Index: mmotm-2.6.29-Feb24/include/linux/cgroup.h
> ===================================================================
> --- mmotm-2.6.29-Feb24.orig/include/linux/cgroup.h
> +++ mmotm-2.6.29-Feb24/include/linux/cgroup.h
> @@ -258,6 +258,8 @@ struct cftype {
> */
> char name[MAX_CFTYPE_NAME];
> int private;
> + /* if not 0, mode is set to mode, otherwise 0644 */
> + int mode;
>
> /*
> * If non-zero, defines the maximum length of string that can
> Index: mmotm-2.6.29-Feb24/kernel/cgroup.c
> ===================================================================
> --- mmotm-2.6.29-Feb24.orig/kernel/cgroup.c
> +++ mmotm-2.6.29-Feb24/kernel/cgroup.c
> @@ -1767,7 +1767,10 @@ int cgroup_add_file(struct cgroup *cgrp,
> BUG_ON(!mutex_is_locked(&dir->d_inode->i_mutex));
> dentry = lookup_one_len(name, dir, strlen(name));
> if (!IS_ERR(dentry)) {
> - error = cgroup_create_file(dentry, 0644 | S_IFREG,
> + int mode = 0644;
> + if (cft->mode)
> + mode = cft->mode;
> + error = cgroup_create_file(dentry, mode | S_IFREG,
> cgrp->root->sb);
> if (!error)
> dentry->d_fsdata = (void *)cft;
>
next prev parent reply other threads:[~2009-02-25 8:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 7:35 [PATCH 1/2] cgroup allow subsys to set default mode of its own file KAMEZAWA Hiroyuki
2009-02-25 7:37 ` [PATCH 2/2] cgroup/memcg show correct file mode KAMEZAWA Hiroyuki
[not found] ` <20090225163729.cc43bd5c.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2009-02-25 8:03 ` Balbir Singh
2009-02-25 8:03 ` Balbir Singh
2009-02-25 8:09 ` Dhaval Giani
[not found] ` <20090225080329.GE11421-SINUvgVNF2CyUtPGxGje5AC/G2K4zDHf@public.gmane.org>
2009-02-25 8:09 ` Dhaval Giani
[not found] ` <20090225163555.d2a0b24c.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2009-02-25 7:37 ` KAMEZAWA Hiroyuki
2009-02-25 8:01 ` [PATCH 1/2] cgroup allow subsys to set default mode of its own file Li Zefan
2009-02-25 8:03 ` Balbir Singh
2009-02-25 8:03 ` Balbir Singh
2009-02-26 21:00 ` Andrew Morton
2009-02-26 21:00 ` Andrew Morton
2009-02-27 0:20 ` KAMEZAWA Hiroyuki
[not found] ` <20090227092031.f42cbbbe.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2009-02-27 5:08 ` Dhaval Giani
2009-02-27 5:12 ` Balbir Singh
2009-02-27 5:08 ` Dhaval Giani
2009-02-27 5:12 ` Balbir Singh
[not found] ` <20090226130005.3282cb02.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2009-02-27 0:20 ` KAMEZAWA Hiroyuki
2009-02-27 0:28 ` Paul Menage
2009-02-27 0:28 ` Paul Menage
2009-02-27 0:38 ` KAMEZAWA Hiroyuki
[not found] ` <6599ad830902261628k4ce8e1aflb7981672562801fb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-02-27 0:38 ` KAMEZAWA Hiroyuki
2009-02-27 0:40 ` Li Zefan
2009-02-27 0:40 ` Li Zefan
2009-02-25 8:01 ` Li Zefan [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-25 7:35 KAMEZAWA Hiroyuki
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=49A4FAC9.2080701@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.