From: Klaus Jensen <its@irrelevant.dk>
To: Gollu Appalanaidu <anaidu.gollu@samsung.com>
Cc: fam@euphon.net, kwolf@redhat.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org, mreitz@redhat.com, stefanha@redhat.com,
kbusch@kernel.org
Subject: Re: [PATCH 2/3] hw/nvme/ctrl: fix endian conversion for nsid in ctrl list
Date: Mon, 31 May 2021 22:53:39 +0200 [thread overview]
Message-ID: <YLVM0wzZvZpaL7OK@apples.localdomain> (raw)
In-Reply-To: <20210517100736.17063-3-anaidu.gollu@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]
On May 17 15:37, Gollu Appalanaidu wrote:
>In Identify Ctrl List of the CNS 0x12 and 0x13 no endian conversion
>for the nsid field.
>
>Signed-off-by: Gollu Appalanaidu <anaidu.gollu@samsung.com>
>---
> hw/nvme/ctrl.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
>diff --git a/hw/nvme/ctrl.c b/hw/nvme/ctrl.c
>index d08a3350e2..813a72c655 100644
>--- a/hw/nvme/ctrl.c
>+++ b/hw/nvme/ctrl.c
>@@ -4255,6 +4255,7 @@ static uint16_t nvme_identify_ctrl_list(NvmeCtrl *n, NvmeRequest *req,
> bool attached)
> {
> NvmeIdentify *c = (NvmeIdentify *)&req->cmd;
>+ uint32_t nsid = le32_to_cpu(c->nsid);
> uint16_t min_id = le16_to_cpu(c->ctrlid);
> uint16_t list[NVME_CONTROLLER_LIST_SIZE] = {};
> uint16_t *ids = &list[1];
>@@ -4265,11 +4266,11 @@ static uint16_t nvme_identify_ctrl_list(NvmeCtrl *n, NvmeRequest *req,
> trace_pci_nvme_identify_ctrl_list(c->cns, min_id);
>
> if (attached) {
>- if (c->nsid == NVME_NSID_BROADCAST) {
>+ if (nsid == NVME_NSID_BROADCAST) {
> return NVME_INVALID_FIELD | NVME_DNR;
> }
>
>- ns = nvme_subsys_ns(n->subsys, c->nsid);
>+ ns = nvme_subsys_ns(n->subsys, nsid);
> if (!ns) {
> return NVME_INVALID_FIELD | NVME_DNR;
> }
>@@ -4281,7 +4282,7 @@ static uint16_t nvme_identify_ctrl_list(NvmeCtrl *n, NvmeRequest *req,
> continue;
> }
>
>- if (attached && !nvme_ns(ctrl, c->nsid)) {
>+ if (attached && !nvme_ns(ctrl, nsid)) {
> continue;
> }
>
>--
>2.17.1
>
I know that the endianness conversion was missing before your patch, but
please squash this up into patch 1.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-05-31 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210517101201epcas5p369289ffa35baa72b248bcc578f009f64@epcas5p3.samsung.com>
2021-05-17 10:07 ` [PATCH 0/3] adding ctrl list (cns 0x13) support and random fixes Gollu Appalanaidu
[not found] ` <CGME20210517101209epcas5p12d9c0d10a0f34a0f62aaf9ef388d51b8@epcas5p1.samsung.com>
2021-05-17 10:07 ` [PATCH 1/3] hw/nvme/ctrl: add controller list cns 0x13 Gollu Appalanaidu
2021-05-31 20:52 ` Klaus Jensen
[not found] ` <CGME20210517101212epcas5p356060d787b2a70309436bf3ecdf1e17c@epcas5p3.samsung.com>
2021-05-17 10:07 ` [PATCH 2/3] hw/nvme/ctrl: fix endian conversion for nsid in ctrl list Gollu Appalanaidu
2021-05-31 20:53 ` Klaus Jensen [this message]
[not found] ` <CGME20210517101216epcas5p1956b513907b466eb10ba392ea8f4b6d3@epcas5p1.samsung.com>
2021-05-17 10:07 ` [PATCH 3/3] hw/nvme/ctrl: documentation fix Gollu Appalanaidu
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=YLVM0wzZvZpaL7OK@apples.localdomain \
--to=its@irrelevant.dk \
--cc=anaidu.gollu@samsung.com \
--cc=fam@euphon.net \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).