| 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
| ||
|
Date: Wed, 31 Jan 2007 10:20:58 -0500 (EST) From: Alan Stern <stern@...land.harvard.edu> To: Robert Hancock <hancockr@...w.ca> cc: linux-kernel <linux-kernel@...r.kernel.org>, Soeren Sonnenburg <kernel@....de> Subject: Re: [linux-usb-devel] 2.6.20-rc6 SCSI error: I/O error - trouble with mass storage devices ?! On Tue, 30 Jan 2007, Robert Hancock wrote: > Alan Stern wrote: > > > The log revealed that the phone's firmware returns garbage values in the > > Residue field for some WRITEs. This patch should take care of it. > > > > Alan Stern > > Is it just me, or should some of these device quirk entries that keep > being added be made unconditional? Adding entries for every single > device that shows up with these problems seems like not a very scalable > approach. These devices obviously work in Windows, can't we just emulate > its behavior here? I have had the same thought... Just because Windows (and a bunch of clueless firmware writers) does something wrong shouldn't mean that we do it too. The fact is, these devices are in violation of the appropriate SCSI and USB specifications. Ignoring the residue value can actually lead to undiscovered errors. According to the spec, it's perfectly legal for a device to return an error indication there and nowhere else. 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/
Powered by blists - more mailing lists