From: James Bottomley <James.Bottomley@steeleye.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Patrick Mansfield <patmans@us.ibm.com>,
Matthew Dharm <mdharm-usb@one-eyed-alien.net>,
USB Storage List <usb-storage@one-eyed-alien.net>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: [linux-usb-devel] [2.6-test] Bug in usb-storage or scsi?
Date: 11 Sep 2003 16:19:16 -0400 [thread overview]
Message-ID: <1063311558.2017.5.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0309111551410.2667-100000@ida.rowland.org>
On Thu, 2003-09-11 at 16:05, Alan Stern wrote:
> What do people think of just having per-device flags that the host driver
> could set during the slave_configure() callback? The point of these flags
> is not to prevent bad commands from being sent to the device --
> user-generated commands sent via sg should always be allowed. Rather, the
> point is to prevent sd.c from generating these commands in the first
> place. (Apparently the commands don't present a problem for sr.c.)
I'm not in principle opposed to this. That's essentially what Andries
did for the mode sense 6 vs 10 problem.
> So for example, usb-storage could set the BFLAG to block MODE-SENSE page 8
> for any disk-type device. This isn't a perfect solution; consider an
> iSCSI-attached device that is actually a usb-storage disk on some server.
> Nevertheless, this might take care of the majority of the problems we see.
> (I haven't seen any MODE-SENSE page 0x3f problems, but others have.)
They can't be BLIST flags, they have to be flags in the struct
scsi_device, but they're easy to add as long as we get a definitive list
of what's necessary.
James
next prev parent reply other threads:[~2003-09-11 20:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[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-10 18:16 ` [usb-storage] " Pat LaVarre
2003-09-10 18:49 ` sg MiB writes scheduling while atomic Pat LaVarre
2003-09-10 19:30 ` Pat LaVarre
2003-09-16 6:35 ` Douglas Gilbert
2003-09-16 11:42 ` Matthew Wilcox
2003-09-16 12:58 ` Christoph Hellwig
2003-10-14 23:36 ` Pat LaVarre
2003-09-10 20:08 ` [PATCH] mount -w of dvd+rw etc. in vanilla 2.6 Pat LaVarre
2003-09-10 22:49 ` Patrick Mansfield
2003-09-22 14:52 ` max GiB written per boot Pat LaVarre
2003-09-10 20:51 ` unsolicited sense in 2.6.0-test5 usb-storage.ko Pat LaVarre
2003-09-10 21:03 ` [usb-storage] " Alan Stern
2003-09-10 21:24 ` Pat LaVarre
2003-09-10 21:52 ` Matthew Dharm
2003-09-10 22:08 ` Pat LaVarre
2003-09-12 0:21 ` Pat LaVarre
2003-09-12 0:29 ` Pat LaVarre
2003-09-16 11:28 ` Douglas Gilbert
2003-09-11 0:02 ` [linux-usb-devel] [2.6-test] Bug in usb-storage or scsi? Patrick Mansfield
2003-09-11 20:04 ` [usb-storage] " Pat LaVarre
2003-09-11 20:05 ` Alan Stern
2003-09-11 20:19 ` James Bottomley [this message]
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
2003-09-10 21:07 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=1063311558.2017.5.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=patmans@us.ibm.com \
--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