From: Xixin Liu <liuxixin@kylinos.cn>
To: linux-nvme@lists.infradead.org
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
linux-kernel@vger.kernel.org, liuxixin@kylinos.cn
Subject: [PATCH v2 2/2] nvme: zns: include zone index in invalid zone type error
Date: Wed, 25 Jun 2026 10:00:00 +0800 [thread overview]
Message-ID: <f6e5d4c3b2a1.v2.1782280600.git.liuxixin@kylinos.cn> (raw)
In-Reply-To: <cover.v2.1782280600.git.liuxixin@kylinos.cn>
Include the zone index when reporting an invalid zone type during zone
descriptor parsing.
Signed-off-by: Xixin Liu <liuxixin@kylinos.cn>
---
drivers/nvme/host/zns.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/nvme/host/zns.c b/drivers/nvme/host/zns.c
index 8ed1b6a33454..b2c3d4e5f6a7 100644
--- a/drivers/nvme/host/zns.c
+++ b/drivers/nvme/host/zns.c
@@ -155,7 +155,8 @@ static int nvme_zone_parse_entry(struct nvme_ns *ns,
struct blk_zone zone = { };
if ((entry->zt & 0xf) != NVME_ZONE_TYPE_SEQWRITE_REQ) {
- dev_err(ns->ctrl->device, "invalid zone type %#x\n", entry->zt);
+ dev_err(ns->ctrl->device, "invalid zone type %#x at zone %u\n",
+ entry->zt, idx);
return -EINVAL;
}
--
2.43.0
next prev parent reply other threads:[~2026-06-26 0:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 5:53 [PATCH v1 0/1] nvme: zns: cap zone report nr_zones by DMA buffer size Xixin Liu
2026-06-24 5:53 ` [PATCH v1 1/1] " Xixin Liu
2026-06-25 11:59 ` Christoph Hellwig
2026-06-25 2:00 ` [PATCH v2 0/2] " Xixin Liu
2026-06-25 2:00 ` Xixin Liu [this message]
2026-06-26 4:50 ` [PATCH v2 2/2] nvme: zns: include zone index in invalid zone type error Christoph Hellwig
2026-06-25 2:00 ` [PATCH v2 1/2] nvme: zns: cap zone report nr_zones by DMA buffer size Xixin Liu
2026-06-26 4:49 ` Christoph Hellwig
2026-07-06 18:55 ` [PATCH v2 0/2] " Keith Busch
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=f6e5d4c3b2a1.v2.1782280600.git.liuxixin@kylinos.cn \
--to=liuxixin@kylinos.cn \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®