From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: Keith Busch <kbusch@kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"sagi@grimberg.me" <sagi@grimberg.me>, "hch@lst.de" <hch@lst.de>
Cc: Michael Nguyen <Michael.Nguyen@wdc.com>
Subject: Re: [PATCH] nvme: ignore zone validate errors on subsequent scans
Date: Fri, 23 Oct 2020 20:34:46 +0000 [thread overview]
Message-ID: <BYAPR04MB4965696830CA41FFF35D2139861A0@BYAPR04MB4965.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20201023191628.1729393-1-kbusch@kernel.org
On 10/23/20 12:22, Keith Busch wrote:
> Revalidating nvme zoned namespaces requires IO commands, and there are
> controller states that prevent IO. For example, a sanitize in progress
> is required to fail all IO, but we don't want to remove a namespace
> we've previously added just because the controller is in such a state.
> Suppress the error in this case.
>
> Reported-by: Michael Nguyen <michael.nguyen@wdc.com>
> Signed-off-by: Keith Busch <kbusch@kernel.org>
> ---
> Yet another reason zone management commands should have been in the
> admin command set!
Agree, I've raised this question.
Looks good.
Reviewed-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-10-23 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 19:16 [PATCH] nvme: ignore zone validate errors on subsequent scans Keith Busch
2020-10-23 20:34 ` Chaitanya Kulkarni [this message]
2020-10-27 9:07 ` 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=BYAPR04MB4965696830CA41FFF35D2139861A0@BYAPR04MB4965.namprd04.prod.outlook.com \
--to=chaitanya.kulkarni@wdc.com \
--cc=Michael.Nguyen@wdc.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;
as well as URLs for NNTP newsgroup(s).