From: Li Zefan <lizf@cn.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Paul Menage <menage@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Containers <containers@lists.linux-foundation.org>
Subject: Re: [PATCH 0/4] cgroups: show correct file mode
Date: Tue, 03 Mar 2009 09:15:42 +0800 [thread overview]
Message-ID: <49AC84BE.5020501@cn.fujitsu.com> (raw)
In-Reply-To: <20090303100827.43d82c3a.kamezawa.hiroyu@jp.fujitsu.com>
>> +/**
>> + * cgroup_file_mode - deduce file mode of a control file
>> + * @cft: the control file in question
>> + *
>> + * returns cftype->mode if ->mode is not 0
>> + * returns 0644 if it has both a read and a write handler
>> + * returns 0444 if it has only a read handler
>> + * returns 0200 if it has only a write hander
>> + */
>> +static int cgroup_file_mode(const struct cftype *cft)
>> +{
>> + int mode = 0;
>> +
>> + if (cft->mode)
>> + return cft->mode;
>> +
>> + if (cft->read || cft->read_u64 || cft->read_s64 ||
>> + cft->read_map || cft->read_seq_string)
>> + mode += 0444;
>> +
>> + if (cft->write || cft->write_u64 || cft->write_s64 ||
>> + cft->write_string || cft->trigger)
>> + mode += 0200;
>> +
>
> += is not |=...
>
Ah, yes, though both happen to result in 0644.
next prev parent reply other threads:[~2009-03-03 1:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 2:13 [PATCH 0/4] cgroups: show correct file mode Li Zefan
2009-03-02 2:13 ` [PATCH 1/4] cgroup debug: " Li Zefan
2009-03-02 2:14 ` [PATCH 2/4] cpuacct: " Li Zefan
2009-03-02 2:15 ` [PATCH 3/4] devcgroup: " Li Zefan
2009-03-02 13:06 ` Serge E. Hallyn
2009-03-02 2:16 ` [PATCH 4/4] cpuset: " Li Zefan
2009-03-02 18:19 ` [PATCH 0/4] cgroups: " Paul Menage
2009-03-03 0:09 ` KAMEZAWA Hiroyuki
2009-03-03 0:15 ` Paul Menage
2009-03-03 0:20 ` KAMEZAWA Hiroyuki
2009-03-03 0:23 ` Paul Menage
2009-03-03 0:23 ` Mike Waychison
2009-03-03 0:26 ` Paul Menage
2009-03-03 1:08 ` Li Zefan
2009-03-03 1:08 ` KAMEZAWA Hiroyuki
2009-03-03 1:15 ` Li Zefan [this message]
2009-03-03 1:19 ` KAMEZAWA Hiroyuki
2009-03-03 1:16 ` Paul Menage
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=49AC84BE.5020501@cn.fujitsu.com \
--to=lizf@cn.fujitsu.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=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