Re: [PATCH 2/3] scsi: add try_rc16 blacklist flag
> "Sitsofe" == Sitsofe Wheeler writes: >> Last time around we identified this as a problem with Microsoft's >> interpretation of the T10 SBC spec. And they promised that they are >> going to fix that. Sitsofe> OK but if we were happy to wait for Microsoft to fix the Sitsofe> problem on the host why were the (broken and incomplete) Sitsofe> BLIST_SKIP_VPD_PAGES patches committed to 3.17 rather than Sitsofe> withdrawn? What's going to be done about those patches now? There are two orthogonal problems. One being that the driver advertised conformance to an old SCSI spec. That's being addressed with the separate SPC-3 patch. The other issue is that thin provisioning is being incorrectly advertised. Because that's being addressed by Microsoft and is an isolated use case I'm hesitant to add quirk for it. Whereas I know several other devices that will benefit from the TRY_VPD_PAGES blacklist option. -- Martin K. Petersen Oracle Linux Engineering -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 2/3] scsi: add try_rc16 blacklist flag
On Tue, Oct 14, 2014 at 09:08:28PM -0400, Martin K. Petersen wrote: > > "Sitsofe" == Sitsofe Wheeler writes: > > Sitsofe> Microsoft Hyper-V virtual disks currently only claim SPC-2 > Sitsofe> compliance causing the kernel skip checks for features such as > Sitsofe> thin provisioning even though the virtual disk advertises them. > > Last time around we identified this as a problem with Microsoft's > interpretation of the T10 SBC spec. And they promised that they are > going to fix that. OK but if we were happy to wait for Microsoft to fix the problem on the host why were the (broken and incomplete) BLIST_SKIP_VPD_PAGES patches committed to 3.17 rather than withdrawn? What's going to be done about those patches now? -- Sitsofe | http://sucs.org/~sits/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [PATCH 2/3] scsi: add try_rc16 blacklist flag
> -Original Message- > From: Martin K. Petersen [mailto:martin.peter...@oracle.com] > Sent: Tuesday, October 14, 2014 6:08 PM > To: Sitsofe Wheeler > Cc: KY Srinivasan; Haiyang Zhang; Christoph Hellwig; Hannes Reinecke; linux- > s...@vger.kernel.org; linux-kernel@vger.kernel.org; > de...@linuxdriverproject.org; James E.J. Bottomley > Subject: Re: [PATCH 2/3] scsi: add try_rc16 blacklist flag > > >>>>> "Sitsofe" == Sitsofe Wheeler writes: > > Sitsofe> Microsoft Hyper-V virtual disks currently only claim SPC-2 > Sitsofe> compliance causing the kernel skip checks for features such as > Sitsofe> thin provisioning even though the virtual disk advertises them. > > Last time around we identified this as a problem with Microsoft's > interpretation of the T10 SBC spec. And they promised that they are going to > fix that. It has been fixed in windows 10 and a bug has been opened for earlier hosts. K. Y > > -- > Martin K. PetersenOracle Linux Engineering -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 2/3] scsi: add try_rc16 blacklist flag
> "Sitsofe" == Sitsofe Wheeler writes: Sitsofe> Microsoft Hyper-V virtual disks currently only claim SPC-2 Sitsofe> compliance causing the kernel skip checks for features such as Sitsofe> thin provisioning even though the virtual disk advertises them. Last time around we identified this as a problem with Microsoft's interpretation of the T10 SBC spec. And they promised that they are going to fix that. -- Martin K. Petersen Oracle Linux Engineering -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
