From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Adrian Hunter <adrian.hunter@nokia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Philip Langdale <philipl@overt.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Schummer Jorg.2 (EXT-Tieto/Espoo)"
<ext-jorg.2.schummer@nokia.com>,
nico@fluxnic.net, nico@marvell.com
Subject: Re: [PATCH] MMC: fix hang if card was removed during suspend and unsafe resume was enabled
Date: Fri, 05 Feb 2010 15:42:43 +0200 [thread overview]
Message-ID: <1265377363.12577.4.camel@maxim-laptop> (raw)
In-Reply-To: <4B6BF02A.2080501@nokia.com>
On Fri, 2010-02-05 at 12:17 +0200, Adrian Hunter wrote:
> ext Andrew Morton wrote:
> > On Fri, 5 Feb 2010 01:18:15 +0200 Maxim Levitsky <maximlevitsky@gmail.com> wrote:
> >
> >> Currently removal of the card leads to del_disk called indirectly by mmc core.
> >> This function expects userspace to be running, which isn't when .resume is called
> >>
> >> Fix that by removing the code that did that in mmc_resume_host. It is possible
> >> because card detection logic will kick it later and remove the card.
> >
> > I don't really understand. The above implies that to trigger this bug,
> > one needs to physically remove the card during a resume operation. ie:
> > a human-vs-computer race. Sounds unlikely?
> >
> > So... exactly what steps does the user need to take to trigger this
> > bug?
> >
> >> Also make mtd workqueue freezeable, so it won't attempt to add/remove the card
> >> while userspace is frozen.
> >>
> >>
> >> diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c
> >> index 30acd52..879d48d 100644
> >> --- a/drivers/mmc/core/core.c
> >> +++ b/drivers/mmc/core/core.c
> >> @@ -1257,7 +1257,6 @@ int mmc_suspend_host(struct mmc_host *host, pm_message_t state)
> >> if (host->caps & MMC_CAP_DISABLE)
> >> cancel_delayed_work(&host->disable);
> >> cancel_delayed_work(&host->detect);
> >> - mmc_flush_scheduled_work();
> >>
> >> mmc_bus_get(host);
> >> if (host->bus_ops && !host->bus_dead) {
> >> @@ -1300,15 +1299,11 @@ int mmc_resume_host(struct mmc_host *host)
> >> mmc_select_voltage(host, host->ocr);
> >> BUG_ON(!host->bus_ops->resume);
> >> err = host->bus_ops->resume(host);
> >> +
> >> if (err) {
> >> printk(KERN_WARNING "%s: error %d during resume "
> >> "(card was removed?)\n",
> >> mmc_hostname(host), err);
> >> - if (host->bus_ops->remove)
> >> - host->bus_ops->remove(host);
> >> - mmc_claim_host(host);
> >> - mmc_detach_bus(host);
> >> - mmc_release_host(host);
> >
> > afacit that code's been there since March 2009. I'd have thought that
> > someone would have noticed "kernel hangs on resume" before now.
> >
> > Do you think the patch should be backported into 2.6.32.x and eariler?
>
> It looks like the code was introduced in 2.6.32.x by commit
>
> 95cdfb72b9bc568803f395c266152c71b034b461
>
> cc'ing the author Nicolas Pitre
I don't think this is this commit fault.
The problem lies somewhere in block layer.
del_disk hangs if called while usrspace is frozen.
Because I assume that this code was tested, I guess that it was possible
to call del_disk in this way once.
Fixing CONFIG_MMC_UNSAFE_RESUME=n not to do del_disk, won't be easy...
Best regards,
Maxim Levitsky
prev parent reply other threads:[~2010-02-05 13:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 17:47 Hand on resume if sd/mmc card was removed while system was suspended/hibernated Maxim Levitsky
2010-02-04 23:18 ` [PATCH] MMC: fix hang if card was removed during suspend and unsafe resume was enabled Maxim Levitsky
2010-02-05 0:09 ` Andrew Morton
2010-02-05 8:31 ` Maxim Levitsky
2010-02-05 14:13 ` Andrew Morton
2010-02-05 14:19 ` Maxim Levitsky
2010-02-05 14:39 ` Andrew Morton
2010-02-05 15:52 ` Maxim Levitsky
2010-02-05 16:19 ` Madhusudhan
2010-02-05 16:32 ` Maxim Levitsky
2010-02-05 18:26 ` Andrew Morton
2010-02-05 19:58 ` Maxim Levitsky
2010-02-05 10:17 ` Adrian Hunter
2010-02-05 13:42 ` Maxim Levitsky [this message]
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=1265377363.12577.4.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=adrian.hunter@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=ext-jorg.2.schummer@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=nico@marvell.com \
--cc=philipl@overt.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
all inboxes | Powered by JetHome®