From: Cedric Le Goater <clg@fr.ibm.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Containers <containers@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/4] freezer_cg: remove redundant check in freezer_can_attach()
Date: Tue, 21 Oct 2008 09:32:50 +0200 [thread overview]
Message-ID: <48FD85A2.8090605@fr.ibm.com> (raw)
In-Reply-To: <48FD273F.3040505@cn.fujitsu.com>
Li Zefan wrote:
> It is sufficient to check if @task is frozen, and no need to check if
> the original freezer is frozen.
hmm, a task being frozen does not mean that its freezer cgroup is
frozen. So the extra check seems valid but looking at the comment :
/*
* The call to cgroup_lock() in the freezer.state write method prevents
* a write to that file racing against an attach, and hence the
* can_attach() result will remain valid until the attach completes.
*/
static int freezer_can_attach(struct cgroup_subsys *ss,
how do we know that the task_freezer(task), which is not protected by
the cgroup_lock(), is not going to change its state to CGROUP_FROZEN
it looks racy.
C.
> Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
> ---
> kernel/cgroup_freezer.c | 16 +++++++---------
> 1 files changed, 7 insertions(+), 9 deletions(-)
>
> diff --git a/kernel/cgroup_freezer.c b/kernel/cgroup_freezer.c
> index 7f54d1c..6fadafe 100644
> --- a/kernel/cgroup_freezer.c
> +++ b/kernel/cgroup_freezer.c
> @@ -162,9 +162,13 @@ static int freezer_can_attach(struct cgroup_subsys *ss,
> struct task_struct *task)
> {
> struct freezer *freezer;
> - int retval;
>
> - /* Anything frozen can't move or be moved to/from */
> + /*
> + * Anything frozen can't move or be moved to/from.
> + *
> + * Since orig_freezer->state == FROZEN means that @task has been
> + * frozen, so it's sufficient to check the latter condition.
> + */
>
> if (is_task_frozen_enough(task))
> return -EBUSY;
> @@ -173,13 +177,7 @@ static int freezer_can_attach(struct cgroup_subsys *ss,
> if (freezer->state == CGROUP_FROZEN)
> return -EBUSY;
>
> - retval = 0;
> - task_lock(task);
> - freezer = task_freezer(task);
> - if (freezer->state == CGROUP_FROZEN)
> - retval = -EBUSY;
> - task_unlock(task);
> - return retval;
> + return 0;
> }
>
> static void freezer_fork(struct cgroup_subsys *ss, struct task_struct *task)
next prev parent reply other threads:[~2008-10-21 7:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 0:48 [PATCH 1/4] freezer_cg: fix improper BUG_ON() causing oops Li Zefan
2008-10-21 0:50 ` [PATCH 2/4] freezer_cg: remove redundant check in freezer_can_attach() Li Zefan
2008-10-21 0:51 ` [PATCH 3/4] freezer_cg: use thaw_process() in unfreeze_cgroup() Li Zefan
2008-10-21 0:52 ` [PATCH 4/4] freezer_cg: simplify freezer_change_state() Li Zefan
2008-10-21 9:53 ` Cedric Le Goater
2008-10-21 21:45 ` Matt Helsley
2008-10-21 7:16 ` [PATCH 3/4] freezer_cg: use thaw_process() in unfreeze_cgroup() Cedric Le Goater
2008-10-21 8:40 ` Li Zefan
2008-10-21 20:58 ` Andrew Morton
2008-10-22 7:37 ` Cedric Le Goater
2008-10-21 21:44 ` Matt Helsley
2008-10-21 7:32 ` Cedric Le Goater [this message]
2008-10-21 9:29 ` [PATCH 2/4] freezer_cg: remove redundant check in freezer_can_attach() Li Zefan
2008-10-21 9:47 ` Cedric Le Goater
2008-10-21 21:40 ` Matt Helsley
2008-10-21 7:16 ` [PATCH 1/4] freezer_cg: fix improper BUG_ON() causing oops Cedric Le Goater
2008-10-21 21:39 ` Matt Helsley
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=48FD85A2.8090605@fr.ibm.com \
--to=clg@fr.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.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