From: Xixin Liu <liuxixin@kylinos.cn>
To: linux-nvme@lists.infradead.org
Cc: hch@lst.de, sagi@grimberg.me, kch@nvidia.com, liuxixin@kylinos.cn
Subject: [PATCH nvmet-v1 0/1] nvmet: zns: reject full zone report when buffer is too small
Date: Thu, 9 Jul 2026 14:51:39 +0800 [thread overview]
Message-ID: <cover.1783579899.git.liuxixin@kylinos.cn> (raw)
Hi,
A Zone Management Receive partial report (PR bit set) may return fewer zone
descriptors than zones matched. A full report (PR bit clear) must fit
every matching descriptor in the data buffer.
nvmet already caps Number of Zones on partial reports, but may return success
on a full report when the buffer is too small. Reject those commands with
INVALID_FIELD.
Tested on nvmet-tcp loopback with io-passthru.
Thanks,
Xixin Liu
---
Xixin Liu (1):
nvmet: zns: reject full zone report when buffer is too small
drivers/nvme/target/zns.c | 15 ++++++++++++---
1 file changed, 12 insertions(+), 3 deletions(-)
--
2.43.0
next reply other threads:[~2026-07-09 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 6:51 Xixin Liu [this message]
2026-07-09 6:51 ` [PATCH nvmet-v1 1/1] nvmet: zns: reject full zone report when buffer is too small Xixin Liu
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=cover.1783579899.git.liuxixin@kylinos.cn \
--to=liuxixin@kylinos.cn \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--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