From: James Bottomley <James.Bottomley@SteelEye.com>
To: Matthew Dharm <mdharm-usb@one-eyed-alien.net>
Cc: Timothy Thelin <Timothy.Thelin@wdc.com>,
t.schorpp@gmx.de, usb-storage@lists.one-eyed-alien.net,
linux-ide@vger.kernel.org,
Linux SCSI list <linux-scsi@vger.kernel.org>
Subject: Re: [usb-storage] [Merging ATA passthru] on integrating SMART/ATA-Security in usb-storage driver
Date: Thu, 03 Nov 2005 23:08:07 -0500 [thread overview]
Message-ID: <1131077287.3117.22.camel@mulgrave> (raw)
In-Reply-To: <20051102234532.GC26148@one-eyed-alien.net>
On Wed, 2005-11-02 at 15:45 -0800, Matthew Dharm wrote:
> On Wed, Nov 02, 2005 at 02:18:52PM -0800, Timothy Thelin wrote:
> >
> > If you had time to spare, instead of touching usb-storage,
> > it might be better spent resurecting SG_FLAG_LUN_INHIBIT to
> > stop the above behavior so that SG_IO cdbs can be passed
> > through untouched.
> > (SG_FLAG_FUN_INHIBIT was a flag SG_IO used to support a long
> > time ago, and I have no idea why it was dropped, but it was)
>
> I didn't realize that had been removed. Anyone that sends a
> vendor-specific command to a device needs this flag to make sure it goes
> through unmangled.
>
> Perhaps someone on linux-scsi can comment on why this was removed and how
> we might get it back?
I've no distinct recollection of someone removing this, but if I
remember correctly what it used to do, it was a hack to stop us from
mangling SCSI-3 CDB's. We fixed the mid-layer not to require the hack
by only setting the CDB[1] lun field for SCSI-1 and SCSI-2 devices (as
the standards mandate). What's the actual problem? No SCSI-1 or SCSI-2
device should have any vendor specific CDBs that uses these bits in
CDB[1].
James
next prev parent reply other threads:[~2005-11-04 15:08 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 22:18 [usb-storage] [Merging ATA passthru] on integrating SMART/ATA-Security in usb-storage driver Timothy Thelin
2005-11-02 23:22 ` thomas schorpp
2005-11-02 23:45 ` Matthew Dharm
2005-11-04 4:08 ` James Bottomley [this message]
2005-11-04 17:28 ` Matthew Dharm
2005-11-04 18:33 ` James Bottomley
2005-11-04 20:30 ` Matthew Dharm
2005-11-04 20:53 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2005-11-08 19:50 Timothy Thelin
2005-11-09 9:04 ` thomas schorpp
2005-11-09 9:45 ` thomas schorpp
2005-11-09 10:05 ` thomas schorpp
2005-11-09 13:21 ` Mark Lord
2005-11-09 14:05 ` thomas schorpp
2005-11-07 20:18 Timothy Thelin
2005-11-07 17:51 Timothy Thelin
2005-11-04 18:30 Timothy Thelin
2005-11-04 18:58 ` James Bottomley
2005-11-04 20:30 ` Matthew Dharm
2005-11-04 20:49 ` James Bottomley
2005-11-05 23:55 ` Matthew Dharm
2005-11-06 0:49 ` James Bottomley
2005-11-06 3:38 ` thomas schorpp
2005-11-06 21:58 ` Matthew Dharm
2005-11-06 22:28 ` thomas schorpp
2005-11-06 23:52 ` Patrick Mansfield
2005-11-07 16:59 ` Matthew Dharm
2005-11-07 17:05 ` Matthew Dharm
2005-11-07 17:24 ` Patrick Mansfield
2005-11-07 17:46 ` Alan Stern
2005-11-07 18:06 ` thomas schorpp
2005-11-07 19:33 ` Alan Stern
2005-11-07 20:07 ` thomas schorpp
2005-11-07 17:53 ` Christoph Hellwig
2005-11-07 17:54 ` thomas schorpp
2005-11-07 18:57 ` Patrick Mansfield
2005-11-07 19:53 ` Alan Stern
2005-11-07 20:47 ` Patrick Mansfield
2005-11-07 20:59 ` Alan Stern
2005-11-07 22:05 ` James Bottomley
2005-11-08 17:09 ` Alan Stern
2005-11-08 23:05 ` Mike Anderson
2005-11-09 15:35 ` Alan Stern
2005-11-06 23:15 ` James Bottomley
2005-11-07 18:14 ` Patrick Mansfield
2005-11-04 23:56 ` Andries Brouwer
2005-11-04 23:46 ` Pete Zaitcev
2005-11-05 16:20 ` thomas schorpp
2005-11-02 20:33 Timothy Thelin
2005-11-02 21:55 ` thomas schorpp
2005-11-02 14:08 thomas schorpp
2005-11-02 16:05 ` [usb-storage] " Alan Stern
2005-11-02 19:12 ` thomas schorpp
2005-11-02 19:26 ` Alan Stern
2005-11-02 20:41 ` thomas schorpp
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=1131077287.3117.22.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Timothy.Thelin@wdc.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=t.schorpp@gmx.de \
--cc=usb-storage@lists.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;
as well as URLs for NNTP newsgroup(s).