From: brooks@netgate.net
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Mike Anderson <andmike@linux.vnet.ibm.com>,
linux-hotplug@vger.kernel.org, Brian.Fehling@citrix.com,
xen@netgate.net,
cases.634568.7962_21175.de8b732451@cases.netsuite.com,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Bug in the scsi_id (0.9 version) utility
Date: Mon, 17 Mar 2008 11:38:41 -0700 (PDT) [thread overview]
Message-ID: <alpine.LRH.1.00.0803171135420.30028@ss.netgate.net> (raw)
In-Reply-To: <1205501914.2904.9.camel@localhost.localdomain>
> This is incorrect; SPC does specify zero in reserved fields.
>
>> The SAM definitions section and the SPC Keywords section provides a
>> definition of what should be in a reserved field.
Thanks for the clarification. I've submitted the bug to OpenSolaris.
>> That said we are not required to be checking the reserved fields for zero
>> but in this case we are doing so to work around another device issue.
>>
>> Instead of adding yet another device work around to the "if" which
>> makes it hard to rework the code in the future as you do not know how many
>> vendor, models are running through certain non compliant checks (i.e. more
>> than the intend models may exhibit like behavior).
>>
>> We possible should look at updating how we handle not compliant behavior.
>> scsi_id.config is available but that must not be useful in all cases as
>> the standard page 83 code has a check for the pre-spc3-83 case even though
>> it is selectable through the config file and command line.
>
> Some type of blacklist might work: we're already starting to find USB
> devices that aren't too happy with VPD inquiries.
That makes sense. Please let me know what you decide, and if there's
anything more I can do to help.
Kevin
next prev parent reply other threads:[~2008-03-17 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LRH.1.00.0803130824450.30028@ss.netgate.net>
2008-03-14 6:08 ` Bug in the scsi_id (0.9 version) utility Mike Anderson
2008-03-14 13:38 ` James Bottomley
2008-03-17 18:38 ` brooks [this message]
2008-03-18 20:15 ` Patrick Mansfield
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=alpine.LRH.1.00.0803171135420.30028@ss.netgate.net \
--to=brooks@netgate.net \
--cc=Brian.Fehling@citrix.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=andmike@linux.vnet.ibm.com \
--cc=cases.634568.7962_21175.de8b732451@cases.netsuite.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=xen@netgate.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