linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: rjw@sisk.pl, pavel@ucw.cz, len.brown@intel.com,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PM/Freezer: Thaw only kernel threads if freezing of kernel threads fails
Date: Wed, 1 Feb 2012 14:36:47 -0800	[thread overview]
Message-ID: <20120201223647.GB19837@google.com> (raw)
In-Reply-To: <20120201223105.6669.12718.stgit@srivatsabhat.in.ibm.com>

On Thu, Feb 02, 2012 at 04:01:12AM +0530, Srivatsa S. Bhat wrote:
> If freezing of kernel threads fails, we are expected to automatically thaw
> tasks in the error recovery path. However, at times, we encounter situations
> in which we would like the automatic error recovery path to thaw only the
> kernel threads, because we want to be able to do some more cleanup before
> we thaw userspace. Something like:
> 
> error = freeze_kernel_threads();
> if (error) {
> 	/* Do some cleanup */
> 
> 	/* Only then thaw userspace tasks*/
> 	thaw_processes();
> }
> 
> An example of such a situation is where we freeze/thaw filesystems during
> suspend/hibernation. There, if freezing of kernel threads fails, we would
> like to thaw the frozen filesystems before thawing the userspace tasks.
> 
> So, modify freeze_kernel_threads() to thaw only kernel threads in case of
> freezing failure.
> 
> Signed-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>

Acked-by: Tejun Heo <tj@kernel.org>

with nits below,

> ---
> 
>  kernel/power/power.h   |   26 ++++++++++++++++++++++++--
>  kernel/power/process.c |    7 +++++--
>  2 files changed, 29 insertions(+), 4 deletions(-)
> 
> diff --git a/kernel/power/power.h b/kernel/power/power.h
> index 0c4defe..cf41c03 100644
> --- a/kernel/power/power.h
> +++ b/kernel/power/power.h
> @@ -231,8 +231,30 @@ extern int pm_test_level;
>  #ifdef CONFIG_SUSPEND_FREEZER
>  static inline int suspend_freeze_processes(void)
>  {
> -	int error = freeze_processes();
> -	return error ? : freeze_kernel_threads();
> +	int error;
> +
> +	error = freeze_processes();
> +
> +	/*
> +	 * freeze_processes() automatically thaws
> +	 * every task if freezing fails. So we need
> +	 * not do anything extra upon error.
> +	 */
> +	if (error)
> +		goto Finish;
> +
> +	error = freeze_kernel_threads();
> +
> +	/*
> +	 * freeze_kernel_threads() thaws only kernel
> +	 * threads upon freezing failure. So we have
> +	 * to thaw the userspace tasks ourselves.
> +	 */
> +	if (error)
> +		thaw_processes();
> +
> + Finish:
> +	return error;

Heh, the original ?: code was scary.  That said, IMHO, the above seems
a bit too verbose.  Functions usually shouldn't have side effects on
failure and the above code is usual in that sense and it would be nice
to mention the reformatting (from cryptic to sane) in the commit log.
Also, how many columns are you flowing the text to?  It seems quite
narrower than they usually should be.

Thanks.

-- 
tejun

  reply	other threads:[~2012-02-01 22:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 22:31 [PATCH] PM/Freezer: Thaw only kernel threads if freezing of kernel threads fails Srivatsa S. Bhat
2012-02-01 22:36 ` Tejun Heo [this message]
2012-02-01 22:49   ` Rafael J. Wysocki
2012-02-01 22:59   ` Srivatsa S. Bhat
2012-02-02  3:15     ` Nigel Cunningham
2012-02-02 19:38     ` Rafael J. Wysocki
2012-02-04 14:11     ` [PATCH Updated] " Srivatsa S. Bhat
2012-02-04 22:27       ` Rafael J. Wysocki
2012-02-05  6:06         ` Hillf Danton
2012-02-05 10:57           ` Srivatsa S. Bhat
2012-02-05 11:09             ` Rafael J. Wysocki
2012-02-05 11:31             ` Hillf Danton
2012-02-05 10:59           ` Rafael J. Wysocki

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=20120201223647.GB19837@google.com \
    --to=tj@kernel.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=srivatsa.bhat@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).