From: Pat LaVarre <p.lavarre@ieee.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-scsi@vger.kernel.org,
Matthew Dharm <mdharm-scsi@one-eyed-alien.net>,
Alex Sanks <alex@netchip.com>, Julian Back <jback@mpc-data.co.uk>,
David Brownell <david-b@pacbell.net>
Subject: Re: bCWBCBLength is cb length no when
Date: 05 Dec 2003 12:29:25 -0700 [thread overview]
Message-ID: <1070652564.12411.436.camel@patibmrh9> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0312051351420.645-100000@ida.rowland.org>
> > > Incidentally, Pat, can you confirm whether bInterfaceSubClass x01 = RBC
> > > (Reduced Block Commands, T10 project 1240-D) uses 0-padding of commands to
> > > 12 bytes or not? The Linux usb-storage driver seems to think that it
> > > doesn't.
> >
> > I can neither concisely confirm, nor concisely deny, sorry.
> ...
> Since usb-storage uses the a+b+d interpretation, that's what I'm inclined
> to go with until more evidence arrives. But to be safe, it might be best
> to accept commands either with or without padding.
Oh, aye, sorry I answered with host context in mind, certainly I agree
"be liberal in what you accept" when speaking as the device receiving
the cdb.
Since as a device we know what the cdb[0] op means, we can develop an
independent idea of how long the cdb is. With dreary conventionality,
let's call that length Do, and say Ho = bCBWCBLength. Then concisely we
conclude:
1) Do = Ho everybody happy.
2) Ho < Do miscompare on purpose by quietly discarding cdb bytes out,
especially if Ho is 12 and/or pad is zero (rather than the other popular
choices of xFF and of copy of cb length)
3) Do < Ho miscompare on purpose by quietly fabricating zero pad.
That's the choice I shipped as usb/atapi bridge, mostly it works.
Something like (3) is explicitly required by 99 Sep bbb: text defining
CBW says something about device shall ignore cb bits past the cb length.
Sorry to say, yes actually I have seen (3) necessary to make sense of
the misspelled -i 8 -y "25 00 00:00:00:00" meaning -i 8 -y "25 00
00:00:00:00 00 00:00 00" i.e. Read Capacity.
> ...
However, since as a device we are aggressively choosing to recover from
the soft error of Do != Ho, ...
Please can we have a way of counting soft errors e.g. please can we have
at least one dmesg per boot to mention this msft/other host design
un/consciously disregarded "be conservative in what you send".
Pat LaVarre
P.S.
> message that came to me was not uuencoded at all.
Thanks for saying, I was curious.
Reverse chronological web trails celebrating "Linux live-CD" distros
defeating annoying Windows limitations include:
http://linux.oreillynet.com/pub/a/linux/2003/11/20/knoppix.html
http://lwn.net/Articles/59504/bigpage
draft not yet connected with ftp put privilege of
http://members.aol.com/plscsi/tools/knoppix/
next prev parent reply other threads:[~2003-12-05 19:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 18:30 usb storage traces Alan Stern
2003-12-04 18:44 ` Matthew Dharm
2003-12-04 20:59 ` Alan Stern
2003-12-04 21:27 ` Matthew Dharm
2003-12-04 21:33 ` Pat LaVarre
2003-12-04 21:34 ` Pat LaVarre
2003-12-04 21:37 ` Pat LaVarre
2003-12-04 21:38 ` Pat LaVarre
2003-12-04 22:24 ` Pat LaVarre
2003-12-04 22:28 ` Pat LaVarre
2003-12-05 3:56 ` Informational Exception mpage [was: usb storage traces] Douglas Gilbert
2003-12-05 15:32 ` Alan Stern
2003-12-05 16:02 ` Pat LaVarre
2003-12-05 15:01 ` usb storage traces Alan Stern
2003-12-05 17:18 ` bCWBCBLength is cb length no when Pat LaVarre
2003-12-05 18:55 ` Alan Stern
2003-12-05 19:29 ` Pat LaVarre [this message]
2003-12-05 17:19 ` usb storage traces Pat LaVarre
2003-12-05 18:22 ` Alan Stern
2003-12-05 5:08 ` Patrick Mansfield
2003-12-05 16:01 ` Alan Stern
2003-12-05 16:11 ` Pat LaVarre
2003-12-05 17:14 ` David Brownell
2003-12-05 17:35 ` Pat LaVarre
2003-12-05 18:21 ` Alan Stern
2003-12-05 18:41 ` Pat LaVarre
2003-12-05 18:24 ` David Brownell
2003-12-16 17:00 ` Randy.Dunlap
2003-12-16 17:07 ` Pat LaVarre
2003-12-05 4:31 ` Douglas Gilbert
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=1070652564.12411.436.camel@patibmrh9 \
--to=p.lavarre@ieee.org \
--cc=alex@netchip.com \
--cc=david-b@pacbell.net \
--cc=jback@mpc-data.co.uk \
--cc=linux-scsi@vger.kernel.org \
--cc=mdharm-scsi@one-eyed-alien.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox