From: Keith Busch <kbusch@fb.com>
To: <linux-nvme@lists.infradead.org>
Cc: <hch@lst.de>, <sagi@grimberg.me>, Keith Busch <kbusch@kernel.org>
Subject: [PATCH] nvme: add bug report info for global duplicate id
Date: Mon, 6 Jun 2022 09:40:47 -0700 [thread overview]
Message-ID: <20220606164047.2549647-1-kbusch@fb.com> (raw)
From: Keith Busch <kbusch@kernel.org>
The recent global id check is finding poorly implemented devices in the
wild. Include relavant device information in the output to help quicken
an appropriate quirk patch.
Signed-off-by: Keith Busch <kbusch@kernel.org>
---
drivers/nvme/host/core.c | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index 24165daee3c8..4cda5024a352 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -3852,6 +3852,13 @@ static int nvme_global_check_duplicate_ids(struct nvme_subsystem *this,
return ret;
}
+static int nvme_str_len(char *s, int len)
+{
+ while (s[len - 1] == ' ')
+ len--;
+ return len;
+}
+
static int nvme_init_ns_head(struct nvme_ns *ns, unsigned nsid,
struct nvme_ns_ids *ids, bool is_shared)
{
@@ -3861,8 +3868,18 @@ static int nvme_init_ns_head(struct nvme_ns *ns, unsigned nsid,
ret = nvme_global_check_duplicate_ids(ctrl->subsys, ids);
if (ret) {
+ struct nvme_subsystem *subsys = ctrl->subsys;
+
dev_err(ctrl->device,
"globally duplicate IDs for nsid %d\n", nsid);
+ dev_err(ctrl->device,
+ "bug report info: VID:%04x model:%.*s firmware:%.*s\n",
+ subsys->vendor_id,
+ nvme_str_len(subsys->model, sizeof(subsys->model)),
+ subsys->model,
+ nvme_str_len(subsys->firmware_rev,
+ sizeof(subsys->firmware_rev)),
+ subsys->firmware_rev);
return ret;
}
--
2.30.2
next reply other threads:[~2022-06-06 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 16:40 Keith Busch [this message]
2022-06-06 17:15 ` [PATCH] nvme: add bug report info for global duplicate id Chaitanya Kulkarni
2022-06-07 10:15 ` Christoph Hellwig
2022-06-07 14:23 ` Keith Busch
2022-06-07 14:44 ` 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=20220606164047.2549647-1-kbusch@fb.com \
--to=kbusch@fb.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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