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 v2 1/2] hw/nvme: fix endianess conversion and add controller list
Date: Mon, 14 Jun 2021 12:01:44 +0200 [thread overview]
Message-ID: <YMcpCKlhXMpyZbaz@apples.localdomain> (raw)
In-Reply-To: <20210613115958.GA20730@2030045822>
[-- Attachment #1: Type: text/plain, Size: 3000 bytes --]
On Jun 13 17:29, Gollu Appalanaidu wrote:
>On Wed, Jun 09, 2021 at 10:22:49PM +0200, Klaus Jensen wrote:
>>On Jun 1 20:32, Gollu Appalanaidu wrote:
>>>Add the controller identifiers list CNS 0x13, available list of ctrls
>>>in NVM Subsystem that may or may not be attached to namespaces.
>>>
>>>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>
>>>
>>>-v2:
>>>Fix the review comments from Klaus and squashed 2nd commit into
>>>1st commit
>>>
>>>---
>>>hw/nvme/ctrl.c | 26 ++++++++++++++++----------
>>>hw/nvme/trace-events | 2 +-
>>>include/block/nvme.h | 1 +
>>>3 files changed, 18 insertions(+), 11 deletions(-)
>>>
>>>diff --git a/hw/nvme/ctrl.c b/hw/nvme/ctrl.c
>>>index 2e7498a73e..813a72c655 100644
>>>--- a/hw/nvme/ctrl.c
>>>+++ b/hw/nvme/ctrl.c
>>>@@ -4251,9 +4251,11 @@ static uint16_t nvme_identify_ns(NvmeCtrl *n, NvmeRequest *req, bool active)
>>> return NVME_INVALID_CMD_SET | NVME_DNR;
>>>}
>>>
>>>-static uint16_t nvme_identify_ns_attached_list(NvmeCtrl *n, NvmeRequest *req)
>>>+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];
>>>@@ -4261,15 +4263,17 @@ static uint16_t nvme_identify_ns_attached_list(NvmeCtrl *n, NvmeRequest *req)
>>> NvmeCtrl *ctrl;
>>> int cntlid, nr_ids = 0;
>>>
>>>- trace_pci_nvme_identify_ns_attached_list(min_id);
>>>+ trace_pci_nvme_identify_ctrl_list(c->cns, min_id);
>>>
>>>- if (c->nsid == NVME_NSID_BROADCAST) {
>>>- return NVME_INVALID_FIELD | NVME_DNR;
>>>- }
>>>+ if (attached) {
>>>+ if (nsid == NVME_NSID_BROADCAST) {
>>>+ return NVME_INVALID_FIELD | NVME_DNR;
>>>+ }
>>>
>>>- ns = nvme_subsys_ns(n->subsys, c->nsid);
>>>- if (!ns) {
>>>- return NVME_INVALID_FIELD | NVME_DNR;
>>>+ ns = nvme_subsys_ns(n->subsys, nsid);
>>>+ if (!ns) {
>>>+ return NVME_INVALID_FIELD | NVME_DNR;
>>>+ }
>>> }
>>>
>>> for (cntlid = min_id; cntlid < ARRAY_SIZE(n->subsys->ctrls); cntlid++) {
>>
>>Assume that `attached` is false and `n->subsys` is NULL.
>>
>>KABOOOOM :)
>
>This scenario has been tested but executed without any issue, since here
>ARRAY_SIZE calculating size as per the "NVME_MAX_CONTROLLERS" defined.
>
Yes, I realized this was compile-time, but still surprising behavior and
not intended ;)
>These two CNS values shows affect when there exists a Subsystem. will add
>check condition if there is no Subsystem will return invalid field in command.
>
>if (!n->subsys) {
> return NVME_INVALID_FIELD | NVME_DNR;
>}
>
Sounds good.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-06-14 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210601150640epcas5p298805b3669ca8b586d92da31d4742ab0@epcas5p2.samsung.com>
2021-06-01 15:02 ` [PATCH v2 1/2] hw/nvme: fix endianess conversion and add controller list Gollu Appalanaidu
[not found] ` <CGME20210601150646epcas5p338004eb387e8e9a104b9d2212c694130@epcas5p3.samsung.com>
2021-06-01 15:02 ` [PATCH v2 2/2] hw/nvme: documentation fix Gollu Appalanaidu
2021-06-09 20:23 ` Klaus Jensen
2021-06-09 20:22 ` [PATCH v2 1/2] hw/nvme: fix endianess conversion and add controller list Klaus Jensen
2021-06-13 11:59 ` Gollu Appalanaidu
2021-06-14 10:01 ` Klaus Jensen [this message]
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=YMcpCKlhXMpyZbaz@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).