From: Stuart Foster <smf.linux@ntlworld.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Ed Tomlinson <edt@aei.ca>, USB list <linux-usb@vger.kernel.org>,
SCSI development list <linux-scsi@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: Kernel 3.10.3 "reset SuperSpeed USB device number 2 using xhci_hcd"
Date: Mon, 29 Jul 2013 17:33:29 +0100 [thread overview]
Message-ID: <51F69959.8070409@ntlworld.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1307291108460.1479-100000@iolanthe.rowland.org>
On 07/29/13 16:23, Alan Stern wrote:
> On Mon, 29 Jul 2013, Martin K. Petersen wrote:
>
>>>>>>> "Alan" == Alan Stern <stern@rowland.harvard.edu> writes:
>>
>> Alan,
>>
>> Alan> It was introduced by commit 98dcc2946adb (SCSI: sd: Update WRITE
>> Alan> SAME heuristics). This commit adds a call to scsi_get_vpd_page()
>> Alan> in sd_read_write_same() without first checking
>> Alan> sd_try_extended_inquiry(). As noted in the latter routine, VPD
>> Alan> inquiries will crash some devices.
>>
>> Is REPORT SUPPORTED OPERATION CODES generally safe on USB devices?
>
> Broadly speaking, practically nothing is safe on USB devices. :-) The
> general rule is: If Windows XP doesn't use the command then it will
> crash something.
>
> In the case of these bug reports, the scsi_report_opcode() call returns
> -EINVAL.
>
>> The reason I didn't wrap the WRITE SAME heuristics in
>> sd_try_extended_inquiry() like I have done with most of the other VPDs
>> is that there are a ton of older SPI/SAS/FC devices that support WRITE
>> SAME just fine.
>>
>>
>> Alan> As far as the stable kernels are concerned, the best thing for now
>> Alan> may simply be to revert it.
>>
>> No go. The above commit fixes issues for somebody else.
>>
>> I could add an explicit check to the sd_read_write_same() function. But
>> how about we do the following instead?
>
> Stuart and Ed, does Martin's patch fix your problem?
>
> Alan Stern
>
>
Hi Alan,
The patch is good for me.
thanks
Stuart Foster
next prev parent reply other threads:[~2013-07-29 16:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51F44125.2040803@ntlworld.com>
2013-07-28 19:28 ` Kernel 3.10.3 "reset SuperSpeed USB device number 2 using xhci_hcd" Alan Stern
[not found] ` <Pine.LNX.4.44L0.1307281505410.18237-100000-pYrvlCTfrz9XsRXLowluHWD2FQJk+8+b@public.gmane.org>
2013-07-29 7:21 ` Stuart Foster
2013-07-29 15:06 ` Martin K. Petersen
2013-07-29 15:23 ` Alan Stern
2013-07-29 15:28 ` Martin K. Petersen
2013-07-29 16:33 ` Stuart Foster [this message]
2013-07-30 18:44 ` Alan Stern
2013-07-31 2:58 ` Martin K. Petersen
2013-07-31 14:50 ` Alan Stern
2013-08-02 10:32 ` Peter Wu
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=51F69959.8070409@ntlworld.com \
--to=smf.linux@ntlworld.com \
--cc=edt@aei.ca \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stable@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.