From: Andrew Morton <akpm@linux-foundation.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org, menage@google.com,
lizf@cn.fujitsu.com, balbir@linux.vnet.ibm.com
Subject: Re: [PATCH 1/2] cgroup allow subsys to set default mode of its own file
Date: Thu, 26 Feb 2009 13:00:05 -0800 [thread overview]
Message-ID: <20090226130005.3282cb02.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090225163555.d2a0b24c.kamezawa.hiroyu@jp.fujitsu.com>
On Wed, 25 Feb 2009 16:35:55 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> 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.
Well, we have compatibility issues here. If we make this change, and
people write tools which depend upon that change then those tools might
break when run upon older kernels. Or they need back-compatibility
additions, which increases the testing burden of those tools.
One way in which we could improve this situation is to backport these
changes into earlier kernels, although I don't know which versions.
What do we think?
next prev parent reply other threads:[~2009-02-26 21:00 UTC|newest]
Thread overview: 13+ 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
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
2009-02-26 21:00 ` Andrew Morton [this message]
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=20090226130005.3282cb02.akpm@linux-foundation.org \
--to=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=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