From: Tejun Heo <tj@kernel.org>
To: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: LKML <linux-kernel@vger.kernel.org>,
cgroups <cgroups@vger.kernel.org>,
Ben Blum <bblum@andrew.cmu.edu>, Li Zefan <lizefan@huawei.com>
Subject: Re: [REGRESSION] cgroup: notify_on_release may not be triggered in some cases
Date: Tue, 16 Oct 2012 17:11:42 -0700 [thread overview]
Message-ID: <20121017001142.GN16166@google.com> (raw)
In-Reply-To: <20121004163716.64dae034dab9eafa2b6e6a8f@mxp.nes.nec.co.jp>
Hello,
On Thu, Oct 04, 2012 at 04:37:16PM +0900, Daisuke Nishimura wrote:
> notify_on_release must be triggered when the last process in a cgroup is
> move to another. But if the first(and only) process in a cgroup is moved to
> another, notify_on_release is not triggered.
>
> # mkdir /cgroup/cpu/SRC
> # mkdir /cgroup/cpu/DST
> #
> # echo 1 >/cgroup/cpu/SRC/notify_on_release
> # echo 1 >/cgroup/cpu/DST/notify_on_release
> #
> # sleep 300 &
> [1] 8629
> #
> # echo 8629 >/cgroup/cpu/SRC/tasks
> # echo 8629 >/cgroup/cpu/DST/tasks
> -> notify_on_release for /SRC must be triggered at this point,
> but it isn't.
>
> This is because put_css_set() is called before setting CGRP_RELEASABLE
> in cgroup_task_migrate(), and is a regression introduce by the
> commit:74a1166d(cgroups: make procs file writable), which was merged
> into v3.0.
>
> Cc: Ben Blum <bblum@andrew.cmu.edu>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Li Zefan <lizefan@huawei.com>
> Cc: <stable@vger.kernel.org> # v3.0.x and later
> Signed-off-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Applied to cgroup/for-3.7-fixes w/ Li's ack added.
Thanks!
--
tejun
prev parent reply other threads:[~2012-10-17 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 7:37 [REGRESSION] cgroup: notify_on_release may not be triggered in some cases Daisuke Nishimura
2012-10-08 6:11 ` Li Zefan
2012-10-17 0:11 ` Tejun Heo [this message]
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=20121017001142.GN16166@google.com \
--to=tj@kernel.org \
--cc=bblum@andrew.cmu.edu \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=nishimura@mxp.nes.nec.co.jp \
/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