From: Pat LaVarre <p.lavarre@ieee.org>
To: stern@rowland.harvard.edu
Cc: mdharm-usb@one-eyed-alien.net, usb-storage@one-eyed-alien.net,
linux-scsi@vger.kernel.org
Subject: Re: [linux-usb-devel] [2.6-test] Bug in usb-storage or scsi?
Date: 10 Sep 2003 15:07:08 -0600 [thread overview]
Message-ID: <1063228028.6151.1.camel@patehci2> (raw)
I see Google didn't thread my first try properly, sorry. Here I am
again with an edited subject line.
-----Forwarded Message-----
From: Pat LaVarre <p.lavarre@ieee.org>
To: stern@rowland.harvard.edu
Cc: mdharm-usb@one-eyed-alien.net, usb-storage@one-eyed-alien.net, linux-scsi@vger.kernel.org
Subject: Re: [usb-storage] Re: [linux-usb-devel] [2.6-test] Bug in usb-storage or scsi?
Date: 10 Sep 2003 12:16:31 -0600
> What do the SCSI folk have to say about it?
Anyone?
> > for 2.6.0 ... drivers/scsi/sd.c ...
> > sd_read_cache_type ...
> > Get rid of (or #ifdef out) most ...
>
> Is there any feeling about how to handle these
> ongoing problems with the mode-sense cache
> page?
Yes, much.
Maybe more feeling if you remind/teach me what breaks if we don't fetch
page 8 re Cache. First I imagine automounters mount read-only disks rw,
and then the write cache gets errors while flushing. I wonder what else
breaks. Maybe thruput varies for devices that do or do not bother to
claim they have write cache.
Maybe more feeling if you can say how in/accurate page 8 re Cache
commonly is. For example, I know of no clear & broadly adopted standard
that requires a device to declare write-behind or background defect map
updates as a form of write cache.
> There doesn't seem to be any general solution
> that can work with all USB storage devices.
I understand you to be saying we can settle for an sd solution, we don't
mind if the sd heuristic we discover then doesn't apply to pdt x05
dvd/cd.
> some hang when asked to read just the page
> header.
> ...
> some hang when asked to read just part of the
> page;
> ...
> Some hang when asked to read the entire page;
Device folk ship bugs, aye, same as host folk.
Are not two of these three failures disproportionately common?
Me, I would expect asking anything but what Windows asks would fail most
often. Is that not so? Do we know what Windows asks? Do we know
if/how Win ME/ 2K/ XP differ here? Have we matched CBWCB and
dCBWDataTransferLength in every bit?
Pat LaVarre
next reply other threads:[~2003-09-10 21:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 21:07 Pat LaVarre [this message]
[not found] <3F5E434D.6080801@unixsol.org>
2003-09-10 16:23 ` [linux-usb-devel] [2.6-test] Bug in usb-storage or scsi? Alan Stern
2003-09-11 0:02 ` Patrick Mansfield
2003-09-11 20:05 ` Alan Stern
2003-09-11 20:19 ` James Bottomley
2003-09-12 21:17 ` Alan Stern
2003-09-11 20:42 ` Pat LaVarre
2003-09-12 19:59 ` Alan Stern
2003-09-12 19:18 ` Pat LaVarre
2003-09-12 18:43 ` Pat LaVarre
2003-09-12 20:56 ` Patrick Mansfield
2003-09-12 21:53 ` Pat LaVarre
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=1063228028.6151.1.camel@patehci2 \
--to=p.lavarre@ieee.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@one-eyed-alien.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox