public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Sebastian Ott <sebott@linux.vnet.ibm.com>
Cc: Marcin Slusarz <marcin.slusarz@gmail.com>,
	Linux PM List <linux-pm@lists.linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] 2 bugs related to suspend to disk
Date: Mon, 25 May 2009 23:29:50 +0200	[thread overview]
Message-ID: <200905252329.51274.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.LFD.2.00.0905251614160.4048@localhost.localdomain>

On Monday 25 May 2009, Sebastian Ott wrote:
> hi,
> 
> On Sun, 24 May 2009, Rafael J. Wysocki wrote:
> 
> > On Sunday 24 May 2009, Marcin Slusarz wrote:
> > > 1) echo platform > /sys/power/disk; echo disk > /sys/power/state
> > > 
> > > works but prints:
> > > 
> > > BUG: sleeping function called from invalid context at include/linux/writeback.h:87
> > > in_atomic(): 1, irqs_disabled(): 0, pid: 6509, name: sh
> > > 3 locks held by sh/6509:
> > >  #0:  (&buffer->mutex){+.+.+.}, at: [<>] sysfs_write_file+0x38/0x119
> > >  #1:  (pm_mutex){+.+.+.}, at: [<>] hibernate+0x17/0x169
> > >  #2:  (swap_lock){+.+...}, at: [<>] swap_type_of+0x2e/0xed
> > > Pid: 6509, comm: sh Not tainted 2.6.30-rc7-mod #124
> > > Call Trace:
> > >  ? __debug_show_held_locks
> > >  ? bdev_test
> > >  __might_sleep
> > >  ifind
> > >  ? bdev_test
> > >  iget5_locked
> > >  ? bdev_set
> > >  bdget
> > >  swap_type_of
> > >  swsusp_write
> > >  ? acpi_sleep_tts_switch
> > >  hibernate
> > >  state_store
> > >  kobj_attr_store
> > >  sysfs_write_file
> > >  vfs_write
> > >  sys_write
> > >  system_call_fastpath
> > > 
> > > 2) "s2disk" (from suspend-0.8) suspends, but doesn't resume (and I need to mkswap && swapon -a later)
> > > 
> > > It's not a regression, because I never tried to STD (STR worked).
> > 
> > Both look strange, at least the first one does.
> > 
> > Thanks for the report, I'll do my best to take care of this as soon as I can.
> > 
> 
> i've seen a similar warning, the problem seems to be that swap_type_of 
> calls bdget with the swap_lock held.

Well, it didn't cause any problems in the past.

> with the attached patch i don't see this warning any more - but i'm not 
> sure if this is the correct way to fix this

I'll have a look, thanks for the patch.

> regards, sebastian
> ---
> 
> don't call bdget with swap_lock held
> 
> Signed-off-by: Sebastian Ott <sebott@linux.vnet.ibm.com>
> ---
>  mm/swapfile.c |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> Index: linux-2.5/mm/swapfile.c
> ===================================================================
> --- linux-2.5.orig/mm/swapfile.c	2009-03-24 13:51:00.000000000 +0100
> +++ linux-2.5/mm/swapfile.c	2009-05-25 15:33:34.000000000 +0200
> @@ -634,10 +634,10 @@ int swap_type_of(dev_t device, sector_t 
>  			continue;
>  
>  		if (!bdev) {
> +			spin_unlock(&swap_lock);
>  			if (bdev_p)
>  				*bdev_p = bdget(sis->bdev->bd_dev);
>  
> -			spin_unlock(&swap_lock);
>  			return i;
>  		}
>  		if (bdev == sis->bdev) {
> @@ -646,10 +646,10 @@ int swap_type_of(dev_t device, sector_t 
>  			se = list_entry(sis->extent_list.next,
>  					struct swap_extent, list);
>  			if (se->start_block == offset) {
> +				spin_unlock(&swap_lock);
>  				if (bdev_p)
>  					*bdev_p = bdget(sis->bdev->bd_dev);
>  
> -				spin_unlock(&swap_lock);
>  				bdput(bdev);
>  				return i;
>  			}
> --

Best,
Rafael

  reply	other threads:[~2009-05-25 21:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-24 19:05 2 bugs related to suspend to disk Marcin Slusarz
2009-05-24 19:58 ` Rafael J. Wysocki
2009-05-25 14:56   ` [linux-pm] " Sebastian Ott
2009-05-25 21:29     ` Rafael J. Wysocki [this message]
2009-05-24 20:54 ` Pavel Machek
2009-05-24 21:56   ` Marcin Slusarz
2009-05-24 22:04     ` Rafael J. Wysocki
2009-05-25 17:22       ` Marcin Slusarz
2009-05-25 21:31         ` Rafael J. Wysocki
2009-05-27 19:53           ` Marcin Slusarz
2009-05-27 20:47             ` Rafael J. Wysocki
2009-07-11 14:38               ` Marcin Slusarz

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=200905252329.51274.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=sebott@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