[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1406577767.19418.11.camel@jarvis>
Date: Mon, 28 Jul 2014 20:02:53 +0000
From: James Bottomley <jbottomley@...allels.com>
To: "kys@...rosoft.com" <kys@...rosoft.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"hch@...radead.org" <hch@...radead.org>,
"sitsofe@...il.com" <sitsofe@...il.com>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"apw@...onical.com" <apw@...onical.com>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"ohering@...e.com" <ohering@...e.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"jasowang@...hat.com" <jasowang@...hat.com>
Subject: Re: [PATCH v2 3/3] [SCSI] Make LBP quirk skip lbpme checks tests
On Mon, 2014-07-28 at 19:05 +0000, KY Srinivasan wrote:
>
> > -----Original Message-----
> > From: Martin K. Petersen [mailto:martin.petersen@...cle.com]
> > Sent: Monday, July 28, 2014 12:03 PM
> > To: KY Srinivasan
> > Cc: Martin K. Petersen; Sitsofe Wheeler; Christoph Hellwig;
> > gregkh@...uxfoundation.org; linux-kernel@...r.kernel.org;
> > devel@...uxdriverproject.org; ohering@...e.com; apw@...onical.com;
> > jasowang@...hat.com; jbottomley@...allels.com; linux-
> > scsi@...r.kernel.org
> > Subject: Re: [PATCH v2 3/3] [SCSI] Make LBP quirk skip lbpme checks tests
> >
> > >>>>> "KY" == KY Srinivasan <kys@...rosoft.com> writes:
> >
> > KY,
> >
> > KY> "At the time thin-provisioning was defined, the discovery
> > KY> information was first proposed in READ CAPACITY 16 command. And
> > then
> > KY> moved into the new dedicated VPD page - B2h. You can see the
> > KY> information reported in this VPD page is richer than READ CAPACITY
> > KY> 16 command. As this transition happened during we added the feature,
> > KY> Windows uses the newer method that based on VPD page B2h. It looks
> > KY> Linux tries to use both new and old method which is weird to me."
> >
> > The READ CAPACITY(16) response is not optional.
>
> Ok; that settles the issue then. I will attempt to get it fixed on Windows.
Like Martin says, this isn't optional either/or; it's mandatory to
support the RC 16 bits. If you don't want to get into playing the
messenger between us and the windows guys on SCSI standards, we'd be
happy to communicate directly, either by email or a phone meeting.
James
Powered by blists - more mailing lists