From: Chris Ball <cjb@laptop.org>
To: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
Christoph Hellwig <hch@lst.de>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mmc@vger.kernel.org, viro@zeniv.linux.org.uk
Subject: Re: Regression in suspend to ram in 2.6.31-rc kernels
Date: Fri, 11 Sep 2009 18:22:42 -0400 [thread overview]
Message-ID: <m3k505qfyl.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <c4e36d110909111414n716a06b1mdd0cd741230595b5@mail.gmail.com> (Zdenek Kabelac's message of "Fri, 11 Sep 2009 23:14:08 +0200")
Hi,
> IMHO steps 2..6 are only valid for the case I would 'remove'
> unexpectedly card - but if I suspend and resume my laptop and I
> keep the card inside - all those step looks plain wrong.
How can the MMC stack tell whether you kept the card inside or
modified it during suspend?
There's no way to know, and an incorrect guess gives you filesystem
corruption, so we remove cards on suspend and reprobe them on resume.
(If you did know that cards would never be removed during suspend,
you could set CONFIG_MMC_UNSAFE_RESUME=y.)
So, I'd say:
>> a) card removed event from mmc for suspend is right design?
Yes, for a card containing a filesystem with CONFIG_MMC_UNSAFE_RESUME
not set.
>> b) the card can be changed/removed before system was resumed, mmc
>> can be detect/handle it properly?
Yes, precisely because we removed it before suspend.
>> c) flushing buffers on _deleted_ device is right design?
No, something's obviously gone wrong here.
--
Chris Ball <cjb@laptop.org>
One Laptop Per Child
next prev parent reply other threads:[~2009-09-11 22:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 11:51 Regression in suspend to ram in 2.6.31-rc kernels Zdenek Kabelac
2009-08-31 19:19 ` Rafael J. Wysocki
2009-09-01 9:34 ` Zdenek Kabelac
2009-09-03 22:29 ` Zdenek Kabelac
2009-09-03 23:23 ` Christoph Hellwig
2009-09-04 0:47 ` OGAWA Hirofumi
2009-09-04 9:13 ` Zdenek Kabelac
2009-09-05 17:22 ` OGAWA Hirofumi
2009-09-05 19:53 ` Zdenek Kabelac
2009-09-05 22:42 ` OGAWA Hirofumi
2009-09-08 8:10 ` Zdenek Kabelac
2009-09-09 13:15 ` OGAWA Hirofumi
2009-09-07 12:51 ` Pavel Machek
2009-09-09 13:21 ` OGAWA Hirofumi
2009-09-10 19:23 ` Pavel Machek
2009-09-11 6:39 ` OGAWA Hirofumi
2009-09-11 20:09 ` Pavel Machek
2009-09-11 21:14 ` Zdenek Kabelac
2009-09-11 21:32 ` Pavel Machek
2009-09-11 21:45 ` Zdenek Kabelac
2009-09-11 21:51 ` Pavel Machek
2009-09-11 22:22 ` Rafael J. Wysocki
2009-09-14 20:05 ` Pierre Ossman
2009-09-14 20:25 ` Pavel Machek
2009-09-11 22:29 ` Chris Ball
2009-09-11 22:36 ` Rafael J. Wysocki
2009-09-14 8:39 ` Zdenek Kabelac
2009-09-14 19:17 ` Rafael J. Wysocki
2009-09-14 20:27 ` Pavel Machek
2009-09-18 11:15 ` OGAWA Hirofumi
2009-09-18 21:39 ` Rafael J. Wysocki
2009-09-11 22:22 ` Chris Ball [this message]
2009-09-11 22:04 ` Rafael J. Wysocki
2009-09-11 22:21 ` Pavel Machek
2009-09-11 22:32 ` Rafael J. Wysocki
2009-09-08 19:06 ` Christoph Hellwig
2009-09-08 19:48 ` Rafael J. Wysocki
2009-09-09 13:52 ` OGAWA Hirofumi
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=m3k505qfyl.fsf@pullcord.laptop.org \
--to=cjb@laptop.org \
--cc=hch@lst.de \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=viro@zeniv.linux.org.uk \
--cc=zdenek.kabelac@gmail.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