From: Hannes Reinecke <hare@suse.de>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-scsi@vger.kernel.org,
James Bottomley <james.bottomley@hansenpartnership.com>,
Hannes Reinecke <hare@suse.com>
Subject: Re: [PATCH] scsi: vpd pages are mandatory for SPC-2
Date: Tue, 15 Mar 2016 08:28:42 +0100 [thread overview]
Message-ID: <56E7B9AA.3020302@suse.de> (raw)
In-Reply-To: <yq137rshbrr.fsf@sermon.lab.mkp.net>
On 03/15/2016 12:37 AM, Martin K. Petersen wrote:
>>>>>> "Hannes" == Hannes Reinecke <hare@suse.de> writes:
>
> Hannes,
>
> Hannes> VPD pages 0x0 and 0x83 are mandatory even for SPC-2, so we
> Hannes> should be lowering the restriction to avoid having to whitelist
> Hannes> every SPC-2 compliant device.
>
> I wonder how many non-compliant devices we would have to blacklist as a
> result of this change...
>
But it feels even sillier having to whitelist every
standards-conformant device here; I certainly was when I figured
that EMC Clariion won't work properly without this patch.
And the idea was to mark off _misbehaving_ drives, not the other way
round.
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (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
next prev parent reply other threads:[~2016-03-15 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 13:46 [PATCH] scsi: vpd pages are mandatory for SPC-2 Hannes Reinecke
2016-03-14 23:37 ` Martin K. Petersen
2016-03-15 7:28 ` Hannes Reinecke [this message]
2016-03-15 7:42 ` Christoph Hellwig
2016-03-15 17:19 ` Douglas Gilbert
2016-03-16 8:12 ` Hannes Reinecke
2016-03-15 21:36 ` Martin K. Petersen
2016-03-16 7:38 ` Hannes Reinecke
2016-03-16 7:47 ` Hannes Reinecke
2016-03-23 21:02 ` Martin K. Petersen
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=56E7B9AA.3020302@suse.de \
--to=hare@suse.de \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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).