linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Neukum <oneukum@suse.de>, linux-scsi@vger.kernel.org
Subject: Re: READ_CAPACITY_16 vs. READ_CAPACITY_10
Date: Thu, 12 Sep 2013 07:47:05 +0200	[thread overview]
Message-ID: <52315559.3080708@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1309111010500.1352-100000@iolanthe.rowland.org>

On 09/11/2013 04:14 PM, Alan Stern wrote:
> On Tue, 10 Sep 2013, Oliver Neukum wrote:
> 
>> On Tue, 2013-09-10 at 13:25 -0400, Alan Stern wrote:
>>> On Tue, 10 Sep 2013, Oliver Neukum wrote:
>>>
>>>> Hi Hannes,
>>>>
>>>> you objected to this patch saying there's a possibilty that
>>>> HS devices may also need this feature, which would require
>>>> a quirk. Does this mean that the patch is acceptable only
>>>> with an additional predefined quirk, or do you insist that all
>>>> devices be handled with quirks?
>>>
>>> Indeed, we already know of one or two high-speed devices that suffer
>>> from this bug:
>>>
>>> 	http://marc.info/?l=linux-usb&m=133586313307042&w=2
>>>
>>> This may influence your decision.  I'm not certain whether it is 
>>> important enough to merit a new quirk flag, but people experiencing the 
>>> problem may have some strong opinions.
>>
>> What is the alternative?
> 
> There are three possibilities: nothing, your proposed patch, and a new 
> quirk flag.  The flag is safest, but also the hardest to maintain.
> 
>> I think we can be sure that no drive enclosure will crash
>> with READ_CAPACITY_16.
> 
> I wouldn't count on it, but I don't know of any examples.
> 
Me neither. The whole issue just smells of some firmware coders
messing up their stuff. So I would think that other firmwares
might not have this problem.
(But as HS enclosures aren't that common chances are we've hit
 the same firmware by chance on every test machine we've had.)

I think it would warrant a quirk approach. Yes, it might be slightly
more coding, but at the same time it's more selective on where it
should trigger.
Also looking at scsiglue.c it would make things quite tricky if
you'd want to _disable_ this feature for HS devices; other firmware
from other vendors might not exhibit this issue after all.
And scsiglue.c already has tons of quirks set, adding one more
doesn't do any harm.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-09-12  5:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-10 13:56 READ_CAPACITY_16 vs. READ_CAPACITY_10 Oliver Neukum
2013-09-10 17:25 ` Alan Stern
2013-09-10 20:44   ` Oliver Neukum
2013-09-11 14:14     ` Alan Stern
2013-09-11 15:05       ` Oliver Neukum
2013-09-11 15:42         ` Alan Stern
2013-09-11 15:56           ` Steve Magnani
2013-09-12  5:47       ` Hannes Reinecke [this message]
2013-09-16 12:41         ` Oliver Neukum
2013-09-12  5:56 ` Hannes Reinecke

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=52315559.3080708@suse.de \
    --to=hare@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=oneukum@suse.de \
    --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;
as well as URLs for NNTP newsgroup(s).