From: Douglas Gilbert <dgilbert@interlog.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ltuikov@yahoo.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-usb@vger.kernel.org,
Greg KH <greg@kroah.com>,
James Bottomley <James.Bottomley@suse.de>
Subject: Re: [PATCH repost 3] [SCSI] Retrieve the Caching mode page
Date: Mon, 22 Nov 2010 14:02:06 -0500 [thread overview]
Message-ID: <4CEABE2E.4010609@interlog.com> (raw)
In-Reply-To: <AANLkTi=7tW6wqrk8ZkFuTYwmS-wZ4nQ+jkxk8U95H42F@mail.gmail.com>
On 10-11-22 12:07 PM, Linus Torvalds wrote:
> On Mon, Nov 22, 2010 at 8:56 AM, Luben Tuikov<ltuikov@yahoo.com> wrote:
>>
>> Some kernel transport drivers unconditionally disable
>> retrieval of the Caching mode page. One such for example is
>> the BBB/CBI transport over USB.
>
> One reason for that is that historically we've seen devices that
> simply go crazy - to the point of simply stopping to respond to
> anything - when you ask for pages that Windows doesn't ask for.
>
> It's especially common on USB storage, but it happens elsewhere too.
> The device firmware simply hasn't ever been tested in that situation,
> and it's buggy.
>
> So I don't mind the patch per se, but I think it's potentially way
> more dangerous than it looks.
The vast majority of USB mass storage devices are based
on SCSI-2 (1994) or a particularly nasty standard
called RBC (Reduced Block Commands, 1999) which is a
partial subset of the block commands (i.e. disk related).
We are all aware of the quality of most of the device
end implementations out in the wild.
I believe what Luben is working with is a new standard
called UAS (soon to be ratified) which is based on
www.t10.org work in the last few years. It seems to be
an attempt to throw out the older USB mass storage
transport and do it again, properly.
In the USB domain the UAS transport is identified in
an interface as mass storage class (8), SCSI transparent
command set subclass (6) and protocol 0x62. I would
think that the USB and SCSI layers could be modified to
remove some or all of its mass storage hacks (e.g. disabling
retrieval of the Caching mode page) when the transport
is UAS.
Doug Gilbert
next prev parent reply other threads:[~2010-11-22 19:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 16:56 [PATCH repost 3] [SCSI] Retrieve the Caching mode page Luben Tuikov
2010-11-22 17:07 ` Linus Torvalds
2010-11-22 19:02 ` Douglas Gilbert [this message]
2010-11-23 4:59 ` Matthew Dharm
2010-11-23 18:40 ` Douglas Gilbert
2010-11-22 20:02 ` Luben Tuikov
2010-11-23 5:00 ` Matthew Dharm
2010-11-23 9:25 ` Luben Tuikov
2010-11-23 14:30 ` Matthew Dharm
2010-11-24 9:02 ` Luben Tuikov
2010-11-24 10:10 ` James Bottomley
2010-11-24 14:48 ` Christoph Hellwig
2010-11-24 14:49 ` Alan Stern
2010-11-24 14:58 ` James Bottomley
2010-11-24 16:55 ` Luben Tuikov
-- strict thread matches above, loose matches on Subject: below --
2010-11-23 8:43 Luben Tuikov
2010-12-05 20:53 Luben Tuikov
2010-12-08 0:02 Luben Tuikov
2010-12-08 0:12 ` Greg KH
2010-12-08 5:05 ` James Bottomley
2010-12-08 8:01 ` Luben Tuikov
2010-12-08 15:16 ` Alan Stern
2010-12-08 15:43 ` James Bottomley
2010-12-08 15:57 ` Alan Stern
2010-12-08 16:00 ` Matthew Wilcox
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=4CEABE2E.4010609@interlog.com \
--to=dgilbert@interlog.com \
--cc=James.Bottomley@suse.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ltuikov@yahoo.com \
--cc=torvalds@linux-foundation.org \
/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