linux-kernel - Re: A really interesting mass-storage BUG introduced after 2.6.18

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 for Android: free password hash cracker in your pocket

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

Message-ID: <Pine.LNX.4.44L0.0901141041070.2192-100000@iolanthe.rowland.org>
Date:	Wed, 14 Jan 2009 10:47:05 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Ozan Çağlayan <ozan@...dus.org.tr>
cc:	linux-kernel@...r.kernel.org, <linux-usb@...r.kernel.org>
Subject: Re: A really interesting mass-storage BUG introduced after 2.6.18

On Tue, 13 Jan 2009, [UTF-8] Ozan ÃaÄlayan wrote:

> Here's the usbmon log:
...

Here's the interesting part, right at the end of the log:

> ee5f0e80 2495844993 S Bo:1:011:1 -115 31 = 55534243 02000000 00000000 00000600 00000000 00000000 00000000 000000
> ee5f0e80 2495845078 C Bo:1:011:1 0 31 >
> ee5f0e80 2495845112 S Bi:1:011:2 -115 13 <
> ee5f0e80 2495845327 C Bi:1:011:2 0 13 = 55534253 02000000 00000000 01
> ee5f0e80 2495845338 S Bo:1:011:1 -115 31 = 55534243 03000000 12000000 80000603 00000012 00000000 00000000 000000
> ee5f0e80 2495845579 C Bo:1:011:1 0 31 >
> ee4d7280 2495845595 S Bi:1:011:2 -115 18 <
> ee4d7280 2495845829 C Bi:1:011:2 0 18 = 70000600 0000000a 00000000 3a000000 0000
> ee5f0e80 2495845850 S Bi:1:011:2 -115 13 <
> ee5f0e80 2495845955 C Bi:1:011:2 0 13 = 55534253 03000000 00000000 00

This shows the computer sending a TEST UNIT READY command to the drive, 
and the drive reporting Unit Attention: Media not present.  So of 
course Linux believes there is no media loaded in the drive and doesn't 
try to read the partition table or anything else.

Presumably if the drive is plugged in during bootup then the BIOS does 
something to make this error status go away.  It's hard to guess what 
that would be, however.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/