From: Matthew Dharm <mdharm-scsi@one-eyed-alien.net>
To: Phil Dibowitz <phil@ipom.com>
Cc: Andrew Morton <akpm@osdl.org>, Meelis Roos <mroos@linux.ee>,
Alan Stern <stern@rowland.harvard.edu>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: Fw: garbled usb storage scsi vendor & model in 2.6.19-rc1
Date: Tue, 24 Oct 2006 16:18:16 -0700 [thread overview]
Message-ID: <20061024231816.GD9511@one-eyed-alien.net> (raw)
In-Reply-To: <453E88FA.3070304@ipom.com>
[-- Attachment #1.1: Type: text/plain, Size: 1385 bytes --]
On Tue, Oct 24, 2006 at 02:43:22PM -0700, Phil Dibowitz wrote:
> Alan Stern wrote:
> > There's a comment about this in the source code, asking what should be
> > done if the INQUIRY response is too short (as it is here). Maybe the best
> > approach would be always to assume the first 36 bytes are valid, even when
> > the device says they aren't. It ought to solve your problem, and it's
> > no worse than what we're doing now.
> >
> > The patch is below. This replaces the patch I sent earlier.
>
> Perhaps a better approach might be to set the product and vendor to some
> specific string if the device says it isn't providing one? In the new model,
> can't we still have the chance of showing garbage if the device really isn't
> setting anything useful? So what if we show "Unknown" and "Unknown" or
> something similar in the event that the device sets the 'invalid' bit?
US_FL_FIX_INQUIRY used to do this; I don't remember what it does currently.
Regardless, the SCSI core should probably blank those data buffers before
deciding if any data is going to be copied into them.
Matt
--
Matthew Dharm Home: mdharm-usb@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver
C: Like the Furby?
DP: He gives me the creeps. Think the SPCA will take him?
-- Cobb and Dust Puppy
User Friendly, 1/2/1999
[-- Attachment #1.2: Type: application/pgp-signature, Size: 191 bytes --]
[-- Attachment #2: Type: text/plain, Size: 373 bytes --]
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
[-- Attachment #3: Type: text/plain, Size: 191 bytes --]
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
next prev parent reply other threads:[~2006-10-24 23:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061018223058.65f1cf5e.akpm@osdl.org>
2006-10-19 15:42 ` [linux-usb-devel] Fw: garbled usb storage scsi vendor & model in 2.6.19-rc1 Alan Stern
2006-10-23 4:57 ` Meelis Roos
2006-10-23 14:05 ` [linux-usb-devel] " Alan Stern
2006-10-24 19:35 ` Meelis Roos
2006-10-24 20:30 ` [linux-usb-devel] " Alan Stern
2006-10-24 20:47 ` Meelis Roos
2006-10-24 21:43 ` [linux-usb-devel] " Phil Dibowitz
2006-10-24 23:18 ` Matthew Dharm [this message]
2006-10-25 15:11 ` Alan Stern
2006-10-25 15:08 ` Alan Stern
2006-10-24 22:39 ` Stefan Richter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061024231816.GD9511@one-eyed-alien.net \
--to=mdharm-scsi@one-eyed-alien.net \
--cc=akpm@osdl.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mroos@linux.ee \
--cc=phil@ipom.com \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.