From: Balbir Singh <balbir@linux.vnet.ibm.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>,
"lizf@cn.fujitsu.com" <lizf@cn.fujitsu.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/2] cgroup allow subsys to set default mode of its own file
Date: Wed, 25 Feb 2009 13:33:07 +0530 [thread overview]
Message-ID: <20090225080307.GD11421@balbir.in.ibm.com> (raw)
In-Reply-To: <20090225163555.d2a0b24c.kamezawa.hiroyu@jp.fujitsu.com>
* KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2009-02-25 16:35:55]:
> 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.
Perfect, Thanks, Looks good to me
--
Balbir
next prev parent reply other threads:[~2009-02-25 8:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 7:35 KAMEZAWA Hiroyuki
2009-02-25 7:37 ` [PATCH 2/2] cgroup/memcg show correct file mode KAMEZAWA Hiroyuki
2009-02-25 8:03 ` Balbir Singh
2009-02-25 8:09 ` Dhaval Giani
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 [this message]
2009-02-26 21:00 ` Andrew Morton
2009-02-27 0:20 ` KAMEZAWA Hiroyuki
2009-02-27 5:08 ` Dhaval Giani
2009-02-27 5:12 ` Balbir Singh
2009-02-27 0:28 ` Paul Menage
2009-02-27 0:38 ` KAMEZAWA Hiroyuki
2009-02-27 0:40 ` Li Zefan
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=20090225080307.GD11421@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome