From: Christoph Hellwig <hch@lst.de>
To: "Kenneth R. Crudup" <kenny@panix.com>
Cc: Douglas Gilbert <dgilbert@interlog.com>,
Alan Stern <stern@rowland.harvard.edu>,
Christoph Hellwig <hch@lst.de>,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
linux-usb@vger.kernel.org, usb-storage@lists.one-eyed-alien.net
Subject: Re: Issues with commit 34b48db6 ("block: remove artifical max_hw_sectors cap")
Date: Mon, 5 Jan 2015 18:19:40 +0100 [thread overview]
Message-ID: <20150105171940.GC30028@lst.de> (raw)
In-Reply-To: <alpine.DEB.2.10.1412300830420.12831@tosh-p75a>
On Tue, Dec 30, 2014 at 08:36:34AM -0800, Kenneth R. Crudup wrote:
> OP here. FWIW, this is what I get when running that command on the SCSI
> generic device that corresponds to the USB-3 (non-UAS) disk[1] that had the
> issue:
So it looks like this one actually provides sane values, but we don't
we never even look at EVPD pages for usb devices due to the wrong SCSI
level?
next prev parent reply other threads:[~2015-01-05 17:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.10.1412211420560.4323@tosh-p75a>
2014-12-23 8:31 ` Issues with commit 34b48db6 ("block: remove artifical max_hw_sectors cap") Christoph Hellwig
2014-12-24 7:48 ` Kenneth R. Crudup
2014-12-24 8:18 ` Kenneth R. Crudup
2014-12-27 15:13 ` Christoph Hellwig
2014-12-29 3:10 ` Alan Stern
2014-12-30 11:28 ` Christoph Hellwig
2014-12-30 15:34 ` Alan Stern
2014-12-30 15:50 ` James Bottomley
2014-12-30 16:12 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1412301109050.32416-100000-pYrvlCTfrz9XsRXLowluHWD2FQJk+8+b@public.gmane.org>
2014-12-30 16:25 ` James Bottomley
2014-12-30 16:45 ` Alan Stern
2014-12-30 16:54 ` James Bottomley
2014-12-30 16:19 ` Douglas Gilbert
2014-12-30 16:36 ` Kenneth R. Crudup
2015-01-05 17:19 ` Christoph Hellwig [this message]
2015-01-05 20:07 ` Alan Stern
2015-01-05 20:19 ` Kenneth R. Crudup
2015-01-19 9:45 ` Kenneth R. Crudup
2015-01-19 15:55 ` Alan Stern
2015-01-19 22:59 ` Kenneth R. Crudup
2015-02-08 22:11 ` Kenneth R. Crudup
2015-01-05 17:18 ` Christoph Hellwig
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=20150105171940.GC30028@lst.de \
--to=hch@lst.de \
--cc=dgilbert@interlog.com \
--cc=kenny@panix.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--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