From: Pierre Ossman <pierre@ossman.eu>
To: dsaxena@plexity.net
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MMC: Add 400ms to CAFE SD controller resume path
Date: Sat, 13 Jun 2009 12:34:52 +0200 [thread overview]
Message-ID: <20090613123452.0d24ec82@mjolnir.ossman.eu> (raw)
In-Reply-To: <20090604233349.GA2545@plexity.net>
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]
On Thu, 4 Jun 2009 23:33:49 +0000
Deepak Saxena <dsaxena@plexity.net> wrote:
>
> The request is not ending up in the queue of the new device. If I
> recall correctyl What is happening is that userspace does an unmount on the
> old device when it receives the notification that it is gone (since it is not
> redected and a new entry is created). By the time that unmount is called, the
> various data structures for the device has been zeroed out but the various
> operation pointers are !NULL, so when we go back to write the superblock for
> the mounted partition, we overwrite the device's partition table as the
> partition offset is now 0. The main issue here is that the kernel is allowing
> an I/O to a device that is technically still there but not from the kernel's
> POV.
But if the device is not there from the kernel's POV then it should be
impossible to write to it. It seems this is a kernel bug though. See
this thread:
http://marc.info/?t=124413860500006&r=1&w=2
Rgds
--
-- Pierre Ossman
WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2009-06-13 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 20:05 Deepak Saxena
2009-05-22 11:51 ` Pierre Ossman
2009-05-28 8:36 ` Andrew Morton
2009-05-28 8:48 ` Pierre Ossman
2009-06-04 23:33 ` Deepak Saxena
2009-06-13 10:34 ` Pierre Ossman [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=20090613123452.0d24ec82@mjolnir.ossman.eu \
--to=pierre@ossman.eu \
--cc=akpm@linux-foundation.org \
--cc=dsaxena@plexity.net \
--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
all inboxes | Powered by JetHome®