public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com,
	Len Brown <lenb@kernel.org>
Subject: Re: [PATCH 2/2] resume: wait for device probing to finish
Date: Tue, 13 Jan 2009 01:36:58 +0100	[thread overview]
Message-ID: <200901130136.59293.rjw@sisk.pl> (raw)
In-Reply-To: <20090109211457.6b1d37ed@infradead.org>

On Saturday 10 January 2009, Arjan van de Ven wrote:
> (this patch needs testing on a few different machines; compile tested only)
> 
> 
> From 10b3e25671c817933e232498a56640fd48964345 Mon Sep 17 00:00:00 2001
> From: Arjan van de Ven <arjan@linux.intel.com>
> Date: Fri, 9 Jan 2009 21:11:23 -0800
> Subject: [PATCH] resume: wait for device probing to finish
> 
> the resume code does not currently wait for device probing to finish.
> Even without async function calls this is dicey and not correct,
> but with async function calls during the boot sequence this is going
> to get hit more...
> 
> This patch adds the synchronization using the newly introduced helper.
> 
> Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>

Sorry for the delay, but I only could do the testing today.

It appears that 2.6.29-rc1 with the two patches in this series applied resumes
from hibernation correctly.

Please push the second one to Len with my ack.

Thanks,
Rafael


> ---
>  kernel/power/disk.c |   11 +++++++++++
>  1 files changed, 11 insertions(+), 0 deletions(-)
> 
> diff --git a/kernel/power/disk.c b/kernel/power/disk.c
> index 45e8541..d2d24b7 100644
> --- a/kernel/power/disk.c
> +++ b/kernel/power/disk.c
> @@ -585,6 +585,12 @@ static int software_resume(void)
>  	unsigned int flags;
>  
>  	/*
> +	 * If the user said "noresume".. bail out early.
> +	 */
> +	if (noresume)
> +		return 0;
> +
> +	/*
>  	 * name_to_dev_t() below takes a sysfs buffer mutex when sysfs
>  	 * is configured into the kernel. Since the regular hibernate
>  	 * trigger path is via sysfs which takes a buffer mutex before
> @@ -600,6 +606,11 @@ static int software_resume(void)
>  			mutex_unlock(&pm_mutex);
>  			return -ENOENT;
>  		}
> +		/*
> +		 * Some device discovery might still be in progress; we need
> +		 * to wait for this to finish.
> +		 */
> +		wait_for_device_probe();
>  		swsusp_resume_device = name_to_dev_t(resume_file);
>  		pr_debug("PM: Resume from partition %s\n", resume_file);
>  	} else {
> -- 
> 1.6.0.6

  reply	other threads:[~2009-01-13  0:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-10  5:13 [PATCH 1/2] consolidate driver_probe_done() loops into one place Arjan van de Ven
2009-01-10  5:14 ` [PATCH 2/2] resume: wait for device probing to finish Arjan van de Ven
2009-01-13  0:36   ` Rafael J. Wysocki [this message]
2009-01-25 22:18 ` [PATCH 1/2] consolidate driver_probe_done() loops into one place Greg KH
2009-01-26 16:48   ` Rafael J. Wysocki
2009-01-26 16:59     ` Andrew Morton
2009-01-26 19:18       ` Rafael J. Wysocki
2009-01-26 19:43         ` Greg KH
2009-01-27 15:18           ` 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=200901130136.59293.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=arjan@infradead.org \
    --cc=greg@kroah.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.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