From: Matt Helsley <matthltc@us.ibm.com>
To: Tejun Heo <tj@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Oleg Nesterov <oleg@redhat.com>,
Paul Menage <paul@paulmenage.org>,
containers@lists.linux-foundation.org,
linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH pm-freezer 1/4] cgroup_freezer: fix freezer->state setting bug in freezer_change_state()
Date: Thu, 1 Sep 2011 17:42:31 -0700 [thread overview]
Message-ID: <20110902004231.GF1919@count0.beaverton.ibm.com> (raw)
In-Reply-To: <20110831102100.GA2828@mtj.dyndns.org>
On Wed, Aug 31, 2011 at 12:21:07PM +0200, Tejun Heo wrote:
> d02f52811d0e "cgroup_freezer: prepare for removal of TIF_FREEZE" moved
> setting of freezer->state into freezer_change_state(); unfortunately,
> while doing so, when it's beginning to freeze tasks, it sets the state
> to CGROUP_FROZEN instead of CGROUP_FREEZING ending up skipping the
> whole freezing state. Fix it.
>
> -v2: Oleg pointed out that re-freezing FROZEN cgroup could increment
> system_freezing_cnt. Fixed.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> Reported-by: Oleg Nesterov <oleg@redhat.com>
> Cc: Paul Menage <paul@paulmenage.org>
> Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
> ---
> I'm in the process of moving and can only use a quite old laptop. I
> tested compile but couldn't really do much else, so please proceed
> with caution. Oleg, can you please ack the patches if you agree with
> the updated versions?
>
> Thanks.
>
> kernel/cgroup_freezer.c | 20 +++++++++++---------
> 1 file changed, 11 insertions(+), 9 deletions(-)
>
> Index: work/kernel/cgroup_freezer.c
> ===================================================================
> --- work.orig/kernel/cgroup_freezer.c
> +++ work/kernel/cgroup_freezer.c
> @@ -308,24 +308,26 @@ static int freezer_change_state(struct c
> spin_lock_irq(&freezer->lock);
>
> update_if_frozen(cgroup, freezer);
> - if (goal_state == freezer->state)
> - goto out;
> -
> - freezer->state = goal_state;
>
> switch (goal_state) {
> case CGROUP_THAWED:
> - atomic_dec(&system_freezing_cnt);
> - unfreeze_cgroup(cgroup, freezer);
> + if (freezer->state != CGROUP_THAWED) {
> + freezer->state = CGROUP_THAWED;
> + atomic_dec(&system_freezing_cnt);
> + unfreeze_cgroup(cgroup, freezer);
> + }
> break;
> case CGROUP_FROZEN:
> - atomic_inc(&system_freezing_cnt);
> - retval = try_to_freeze_cgroup(cgroup, freezer);
> + if (freezer->state == CGROUP_THAWED) {
> + freezer->state = CGROUP_FREEZING;
> + atomic_inc(&system_freezing_cnt);
> + retval = try_to_freeze_cgroup(cgroup, freezer);
This still doesn't look quite right. If the cgroup is FREEZING it should
also call try_to_freeze_cgroup(). I think this is what's needed:
if (freezer->state == CGROUP_THAWED)
atomic_inc(&system_freezing_cnt);
freezer->state = CGROUP_FREEZING;
retval = try_to_freeze_cgroup(cgroup, freezer);
> + }
> break;
> default:
> BUG();
> }
Cheers,
-Matt Helsley
next prev parent reply other threads:[~2011-09-02 0:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 10:21 [PATCH pm-freezer 1/4] cgroup_freezer: fix freezer->state setting bug in freezer_change_state() Tejun Heo
2011-08-31 10:21 ` [PATCH pm-freezer 2/4] freezer: set PF_NOFREEZE on a dying task right before TASK_DEAD " Tejun Heo
2011-08-31 10:22 ` [PATCH pm-freezer 3/4] freezer: restructure __refrigerator() Tejun Heo
2011-08-31 10:22 ` [PATCH pm-freezer 4/4] freezer: use lock_task_sighand() in fake_signal_wake_up() Tejun Heo
2011-09-02 17:08 ` [PATCH pm-freezer 3/4] freezer: restructure __refrigerator() Oleg Nesterov
2011-08-31 18:08 ` [PATCH pm-freezer 1/4] cgroup_freezer: fix freezer->state setting bug in freezer_change_state() Oleg Nesterov
2011-09-02 0:42 ` Matt Helsley [this message]
2011-09-02 2:50 ` Tejun Heo
2011-09-02 16:58 ` Oleg Nesterov
2011-09-02 17:08 ` Tejun Heo
2011-09-02 17:15 ` Oleg Nesterov
2011-09-02 17:31 ` Tejun Heo
2011-09-02 17:30 ` Oleg Nesterov
2011-09-02 18:31 ` Matt Helsley
-- strict thread matches above, loose matches on Subject: below --
2011-08-29 14:04 Tejun Heo
2011-08-29 16:00 ` Oleg Nesterov
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=20110902004231.GF1919@count0.beaverton.ibm.com \
--to=matthltc@us.ibm.com \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=oleg@redhat.com \
--cc=paul@paulmenage.org \
--cc=rjw@sisk.pl \
--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