From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:37595)
	by lists.gnu.org with esmtp (Exim 4.71) (envelope-from
	<BATV+b244dc37f40e53d0e5a9+4729+infradead.org+hch@bombadil.srs.infradead.org>)
	id 1bVOXc-0003xG-9X
	for qemu-devel@nongnu.org; Thu, 04 Aug 2016 15:42:53 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from
	<BATV+b244dc37f40e53d0e5a9+4729+infradead.org+hch@bombadil.srs.infradead.org>)
	id 1bVOXb-0006YQ-F5
	for qemu-devel@nongnu.org; Thu, 04 Aug 2016 15:42:52 -0400
From: Christoph Hellwig <hch@lst.de>
Date: Thu,  4 Aug 2016 21:42:13 +0200
Message-Id: <1470339735-30037-1-git-send-email-hch@lst.de>
Subject: [Qemu-devel] fix incorrect identify implementation in nvme
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-block@nongnu.org
Cc: keith.busch@intel.com, qemu-devel@nongnu.org

Third resent of this series after this didn't get picked up the
previous times.  The Qemu NVMe implementation mistakes the cns
field in the Identify command as a boolean.  This was never
true, and is actively harmful since NVMe1.1 (which the Qemu
device claims to support) supports more than two Identify variants.

We had to add a quirk in Linux to work around this behavior.