From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: "Pankaj Raghav" <p.raghav@samsung.com>,
"Javier González" <javier.gonz@samsung.com>,
"Keith Busch" <kbusch@kernel.org>,
"Christoph Hellwig" <hch@lst.de>,
"Sagi Grimberg" <sagi@grimberg.me>,
"Damien Le Moal" <damien.lemoal@opensource.wdc.com>,
"Jens Axboe" <axboe@kernel.dk>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Adam Manzanares <a.manzanares@samsung.com>,
kanchan Joshi <joshi.k@samsung.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Pankaj Raghav <pankydev8@gmail.com>,
Kanchan Joshi <joshiiitr@gmail.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH v2] nvme: Fix zns drives without append support to export correct permissions
Date: Wed, 16 Mar 2022 16:52:07 +0000 [thread overview]
Message-ID: <2d52a62b-209f-e68c-c2f9-dd56af17a18c@nvidia.com> (raw)
In-Reply-To: <20220316093423.17906-1-p.raghav@samsung.com>
On 3/16/22 02:34, Pankaj Raghav wrote:
> This commit 2f4c9ba23b88 ("nvme: export zoned namespaces without Zone
> Append support read-only") exported zoned namespaces without append support
> to be marked as ro. It does it by setting NVME_NS_FORCE_RO to the
> ns->flags in nvme_update_zone_info and later nvme_update_disk_info will
> check for this flag and set the disk as ro.
>
> But later this commit 73d90386b559 ("nvme: cleanup zone information
> initialization") rearranged nvme_update_disk_info to be called before
> nvme_update_zone_info thereby not marking the disk as ro. The call order
> cannot be just reverted because nvme_update_zone_info sets certain queue
> parameters such as zone_write_granularity that depend on the prior call
> to nvme_update_disk_info.
>
> Add a helper nvme_set_disk_ro that can be called in nvme_update_zone_info
> to set the permission for ZNS drives correctly.
>
> Fixes: 73d90386b559 ("nvme: cleanup zone information initialization")
> Signed-off-by: Pankaj Raghav <p.raghav@samsung.com>
> ---
what kind of testing you have done on this patch ?
do you have blktests which addressed this behavior ?
-ck
next prev parent reply other threads:[~2022-03-16 16:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220316093439eucas1p27c2a31849e9dec6c6bc217c5f1b26180@eucas1p2.samsung.com>
2022-03-16 9:34 ` [PATCH v2] nvme: Fix zns drives without append support to export correct permissions Pankaj Raghav
2022-03-16 9:54 ` Chaitanya Kulkarni
2022-03-16 9:56 ` Chaitanya Kulkarni
2022-03-16 10:21 ` Pankaj Raghav
2022-03-16 16:50 ` Chaitanya Kulkarni
2022-03-16 18:03 ` Pankaj Raghav
2022-03-16 10:50 ` Christoph Hellwig
2022-03-16 14:28 ` Pankaj Raghav
2022-03-22 8:39 ` Christoph Hellwig
2022-03-16 16:52 ` Chaitanya Kulkarni [this message]
2022-03-16 18:00 ` Pankaj Raghav
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=2d52a62b-209f-e68c-c2f9-dd56af17a18c@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=a.manzanares@samsung.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hch@lst.de \
--cc=javier.gonz@samsung.com \
--cc=johannes.thumshirn@wdc.com \
--cc=joshi.k@samsung.com \
--cc=joshiiitr@gmail.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mcgrof@kernel.org \
--cc=p.raghav@samsung.com \
--cc=pankydev8@gmail.com \
--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).