From: Li Zefan <lizefan@huawei.com>
To: Tejun Heo <tj@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, cgroups <cgroups@vger.kernel.org>
Subject: Re: [PATCH 2/2] cpuset: remove redundant checks in file write functions
Date: Wed, 14 Aug 2013 10:01:32 +0800 [thread overview]
Message-ID: <520AE4FC.5090702@huawei.com> (raw)
In-Reply-To: <20130813150549.GF26596@mtj.dyndns.org>
On 2013/8/13 23:05, Tejun Heo wrote:
> On Tue, Aug 13, 2013 at 09:17:53AM +0800, Li Zefan wrote:
>> Now cgroup core gets a reference to the css when a cgroup file is
>> opened(), and the reference is dropped at file release. so it's
>> guaranteed the cpuset is online during the write function.
>
> Hmmm... it doesn't really guarantee that as css's can be offlined with
> residual css refcnts, os the css may well be offlined by the time it
> reaches the rw functions. What's guaranteed is that their refcnts
> wouldn't be zero.
Oh, right.
But most controllers don't check this in those read/write functions.
It shoudn't do any harm not checking online/offline status.
> Eventually we need to implement proper sever
> semantics (probably by replacing the custom fs implementation with
> sysfs) but right now controllers still need to deal with offline
> css's.
>
> Thanks.
>
next prev parent reply other threads:[~2013-08-14 2:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 1:17 [PATCH 1/2] cpuset: remove an unncessary forward declaration Li Zefan
2013-08-13 1:17 ` [PATCH 2/2] cpuset: remove redundant checks in file write functions Li Zefan
2013-08-13 2:07 ` Li Zefan
2013-08-13 15:05 ` Tejun Heo
2013-08-14 2:01 ` Li Zefan [this message]
2013-08-14 13:30 ` Tejun Heo
2013-08-16 6:48 ` Li Zefan
2013-08-13 14:53 ` [PATCH 1/2] cpuset: remove an unncessary forward declaration 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=520AE4FC.5090702@huawei.com \
--to=lizefan@huawei.com \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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