linux-kernel - Re: [PATCH] MMC: Add 400ms to CAFE SD controller resume path

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090613123452.0d24ec82@mjolnir.ossman.eu>
Date:	Sat, 13 Jun 2009 12:34:52 +0200
From:	Pierre Ossman <pierre@...man.eu>
To:	dsaxena@...xity.net
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MMC: Add 400ms to CAFE SD controller resume path

On Thu, 4 Jun 2009 23:33:49 +0000
Deepak Saxena <dsaxena@...xity.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.

Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)