From: Christoph Hellwig <hch@lst.de>
To: Yao Sang <sangyao@kylinos.cn>
Cc: linux-nvme@lists.infradead.org, kbusch@kernel.org,
axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
shinichiro.kawasaki@wdc.com
Subject: Re: [PATCH v2] nvme: recompute multipath zoned limits from ready paths
Date: Fri, 22 May 2026 11:21:36 +0200 [thread overview]
Message-ID: <20260522092136.GA8708@lst.de> (raw)
In-Reply-To: <20260522075806.3168366-1-sangyao@kylinos.cn>
On Fri, May 22, 2026 at 03:58:06PM +0800, Yao Sang wrote:
> This was found while debugging a zoned NVMe multipath setup, where the
> namespace head reported 0/0 for max_open_zones and max_active_zones
> while the live path still reported finite limits.
How? Having the different path report different limits is bogus.
I guess we just need to fix it and reject a device with mismatching
parameters.
next prev parent reply other threads:[~2026-05-22 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 7:58 [PATCH v2] nvme: recompute multipath zoned limits from ready paths Yao Sang
2026-05-22 9:21 ` Christoph Hellwig [this message]
2026-05-25 6:40 ` Yao Sang
2026-05-25 7:30 ` 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=20260522092136.GA8708@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=sangyao@kylinos.cn \
--cc=shinichiro.kawasaki@wdc.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