linux-kernel - Re: [linux-usb-devel] 2.6.20-rc6 SCSI error: I/O error

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]

Message-ID: <20070131010353.GA30713@kroah.com>
Date:	Tue, 30 Jan 2007 17:03:53 -0800
From:	Greg KH <greg@...ah.com>
To:	Robert Hancock <hancockr@...w.ca>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	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, Jan 30, 2007 at 05:12:54PM -0600, 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?

If you can figure out a way to dynamically detect broken devices like
this, sure, that would be great.

thanks,

greg k-h
-
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/