From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <keith.busch@intel.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] nvme: fix identify to be NVMe 1.1 compliant
Date: Wed, 18 Nov 2015 20:21:09 +0100 [thread overview]
Message-ID: <20151118192109.GA11825@lst.de> (raw)
In-Reply-To: <1447872792-8508-2-git-send-email-hch@lst.de>
Meh, this was still missing the uncommited changes for the nsid
off by one vs the array index:
diff --git a/hw/block/nvme.c b/hw/block/nvme.c
index 360be71..4f768d5 100644
--- a/hw/block/nvme.c
+++ b/hw/block/nvme.c
@@ -499,10 +499,10 @@ static uint16_t nvme_identify_nslist(NvmeCtrl *n, NvmeIdentify *c)
list = g_malloc0(data_len);
for (i = 0; i < n->num_namespaces; i++) {
- if (i <= min_nsid) {
+ if (i < min_nsid) {
continue;
}
- list[j++] = cpu_to_le32(i);
+ list[j++] = cpu_to_le32(i + 1);
if (j == data_len / sizeof(uint32_t)) {
break;
}
next prev parent reply other threads:[~2015-11-18 19:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 18:53 [Qemu-devel] [PATCH 0/2] import nvme fix Christoph Hellwig
2015-11-18 18:53 ` [Qemu-devel] [PATCH 1/2] nvme: fix identify to be NVMe 1.1 compliant Christoph Hellwig
2015-11-18 19:21 ` Christoph Hellwig [this message]
2015-11-18 18:53 ` [Qemu-devel] [PATCH 2/2] nvme: bump PCI revision Christoph Hellwig
2015-11-25 9:28 ` [Qemu-devel] [Qemu-block] [PATCH 0/2] import nvme fix Kevin Wolf
2015-11-25 16:44 ` Keith Busch
-- strict thread matches above, loose matches on Subject: below --
2016-08-04 19:42 [Qemu-devel] fix incorrect identify implementation in nvme Christoph Hellwig
2016-08-04 19:42 ` [Qemu-devel] [PATCH 1/2] nvme: fix identify to be NVMe 1.1 compliant Christoph Hellwig
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=20151118192109.GA11825@lst.de \
--to=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).