linux-kernel - Re: [linux-usb-devel] 2.6.19-rc1-mm1 - locks when using "dd bs=1M" from card reader

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 23 Oct 2006 10:13:39 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Helge Hafting <helge.hafting@...el.hist.no>
cc:	Christopher Monty Montgomery <xiphmont@...il.com>,
	Paolo Ornati <ornati@...twebnet.it>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	USB development list <linux-usb-devel@...ts.sourceforge.net>
Subject: Re: [linux-usb-devel] 2.6.19-rc1-mm1 - locks when using "dd bs=1M"
 from card reader

On Mon, 23 Oct 2006, Helge Hafting wrote:

> >> During boot I get lots of those "Hardware error, end-of-data detected"
> >> messages, but I've never seen it crash during bootup.
> >>     
> >
> > Those messages are from the card reader.  It doesn't seem to be working 
> > right.  It returns the "end-of-data" error in response to a PREVENT MEDIUM 
> > REMOVAL command
> Unlike a cdrom, it doesn't have the means to prevent media removal. :-)

There's nothing wrong with that; lots of devices don't have the means to 
prevent media removal.  The proper response is "Invalid Command", not "End 
of Data".  If the device sent the proper reply you wouldn't get all those 
"Hardware error, end-of-data detected" messages in the log.

> >  and it returns a phase error in response to a READ 
> > command.  In spite of the fact that it claims to have a 256 MB card 
> > present.
> >   
> It has slots for several different cards, all the other
> slots are empty. 

Were all the slots empty?  If yes, the reader should not have indicated a
card was present in that slot.  If no, the reader should have returned the
data from the card instead of a phase error.  Either way, it misbehaved.

> Perhaps it is broken, but interesting as a "stress-test".
> Linux should not crash because of a bad usb thing, just complain.

Linux did not crash because of the bad reader; it crashed because of an 
unrelated bug in ehci-hcd.  (Although it's possible that the bug was 
triggered by the error-recovery for the bad reader.)

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/