From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: "Javier González" <javier@javigon.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"hch@lst.de" <hch@lst.de>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"mb@lightnvm.io" <mb@lightnvm.io>,
"Javier González" <javier.gonz@samsung.com>,
"SelvaKumar S" <selvakuma.s1@samsung.com>,
"Kanchan Joshi" <joshi.k@samsung.com>,
"Nitesh Shetty" <nj.shetty@samsung.com>
Subject: Re: [PATCH 3/4] nvme: Add consistency check for zone count
Date: Thu, 2 Jul 2020 08:16:37 +0000 [thread overview]
Message-ID: <CY4PR04MB3751A70BE6C1EA7DC930C9C3E76D0@CY4PR04MB3751.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20200702065438.46350-4-javier@javigon.com
On 2020/07/02 15:55, Javier González wrote:
> From: Javier González <javier.gonz@samsung.com>
>
> Since the number of zones is calculated through the reported device
> capacity and the ZNS specification allows to report the total number of
> zones in the device, add an extra check to guarantee consistency between
> the device and the kernel.
>
> Also, fix a checkpatch warning: unsigned -> unsigned int in the process
>
> Signed-off-by: Javier González <javier.gonz@samsung.com>
> Signed-off-by: SelvaKumar S <selvakuma.s1@samsung.com>
> Signed-off-by: Kanchan Joshi <joshi.k@samsung.com>
> Signed-off-by: Nitesh Shetty <nj.shetty@samsung.com>
> ---
> drivers/nvme/host/core.c | 2 +-
> drivers/nvme/host/nvme.h | 6 ++++--
> drivers/nvme/host/zns.c | 39 ++++++++++++++++++++++++++++++++++++++-
> 3 files changed, 43 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
> index 1f5c7fc3d2c9..8b9c69172931 100644
> --- a/drivers/nvme/host/core.c
> +++ b/drivers/nvme/host/core.c
> @@ -1994,7 +1994,7 @@ static int __nvme_revalidate_disk(struct gendisk *disk, struct nvme_id_ns *id)
> case NVME_CSI_NVM:
> break;
> case NVME_CSI_ZNS:
> - ret = nvme_update_zone_info(disk, ns, lbaf);
> + ret = nvme_update_zone_info(disk, ns, lbaf, le64_to_cpu(id->nsze));
> if (ret)
> return ret;
> break;
> diff --git a/drivers/nvme/host/nvme.h b/drivers/nvme/host/nvme.h
> index 662f95fbd909..ef80e0b4df56 100644
> --- a/drivers/nvme/host/nvme.h
> +++ b/drivers/nvme/host/nvme.h
> @@ -407,6 +407,7 @@ struct nvme_ns {
> u32 sws;
> u8 pi_type;
> #ifdef CONFIG_BLK_DEV_ZONED
> + u64 nr_zones;
> u64 zsze;
> #endif
> unsigned long features;
> @@ -700,7 +701,7 @@ static inline void nvme_mpath_start_freeze(struct nvme_subsystem *subsys)
>
> #ifdef CONFIG_BLK_DEV_ZONED
> int nvme_update_zone_info(struct gendisk *disk, struct nvme_ns *ns,
> - unsigned lbaf);
> + unsigned int lbaf, sector_t nsze);
>
> int nvme_report_zones(struct gendisk *disk, sector_t sector,
> unsigned int nr_zones, report_zones_cb cb, void *data);
> @@ -720,7 +721,8 @@ static inline blk_status_t nvme_setup_zone_mgmt_send(struct nvme_ns *ns,
>
> static inline int nvme_update_zone_info(struct gendisk *disk,
> struct nvme_ns *ns,
> - unsigned lbaf)
> + unsigned lbaf
missing a comma here. Does this even compiles ?
> + sector_t nsze)
> {
> dev_warn(ns->ctrl->device,
> "Please enable CONFIG_BLK_DEV_ZONED to support ZNS devices\n");
> diff --git a/drivers/nvme/host/zns.c b/drivers/nvme/host/zns.c
> index b34d2ed13825..d785d179a343 100644
> --- a/drivers/nvme/host/zns.c
> +++ b/drivers/nvme/host/zns.c
> @@ -32,13 +32,36 @@ static int nvme_set_max_append(struct nvme_ctrl *ctrl)
> return 0;
> }
>
> +static u64 nvme_zns_nr_zones(struct nvme_ns *ns)
> +{
> + struct nvme_command c = { };
> + struct nvme_zone_report report;
> + int buflen = sizeof(struct nvme_zone_report);
> + int ret;
> +
> + c.zmr.opcode = nvme_cmd_zone_mgmt_recv;
> + c.zmr.nsid = cpu_to_le32(ns->head->ns_id);
> + c.zmr.slba = cpu_to_le64(0);
> + c.zmr.numd = cpu_to_le32(nvme_bytes_to_numd(buflen));
> + c.zmr.zra = NVME_ZRA_ZONE_REPORT;
> + c.zmr.zrasf = NVME_ZRASF_ZONE_REPORT_ALL;
> + c.zmr.pr = 0;
> +
> + ret = nvme_submit_sync_cmd(ns->queue, &c, &report, buflen);
> + if (ret)
> + return ret;
> +
> + return le64_to_cpu(report.nr_zones);
> +}
> +
> int nvme_update_zone_info(struct gendisk *disk, struct nvme_ns *ns,
> - unsigned lbaf)
> + unsigned int lbaf, sector_t nsze)
> {
> // struct nvme_effects_log *log = ns->head->effects;
> struct request_queue *q = disk->queue;
> struct nvme_command c = { };
> struct nvme_id_ns_zns *id;
> + sector_t cap_nr_zones;
> int status;
>
> /* Driver requires zone append support */
> @@ -80,6 +103,20 @@ int nvme_update_zone_info(struct gendisk *disk, struct nvme_ns *ns,
> goto free_data;
> }
>
> + ns->nr_zones = nvme_zns_nr_zones(ns);
> + if (!ns->nr_zones) {
> + status = -EINVAL;
> + goto free_data;
> + }
> +
> + cap_nr_zones = nvme_lba_to_sect(ns, le64_to_cpu(nsze)) >> ilog2(ns->zsze);
> + if (ns->nr_zones != cap_nr_zones) {
> + dev_err(ns->ctrl->device, "inconsistent zone count: %llu/%llu\n",
> + ns->nr_zones, cap_nr_zones);
> + status = -EINVAL;
> + goto free_data;
> + }
> +
I am not opposed to this, but I am not sure if this adds anything to the checks
in blk_revalidate_disk_zones() as that does a full zone report that is checked
against capacity. This seems more like a test of the drive conformance, checking
that the report header nr_zones is correct...
> q->limits.zoned = BLK_ZONED_HM;
> q->zone_flags = BLK_ZONE_REP_CAPACITY | BLK_ZONE_REP_OFFLINE;
> blk_queue_flag_set(QUEUE_FLAG_ZONE_RESETALL, q);
>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2020-07-02 8:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 6:54 [V2 PATCH 0/4] ZNS: Extra features for current patche Javier González
2020-07-02 6:54 ` [PATCH 1/4] block: Add zone flags to queue zone prop Javier González
2020-07-02 7:54 ` Damien Le Moal
2020-07-02 8:34 ` Javier González
2020-07-02 8:49 ` Damien Le Moal
2020-07-02 10:27 ` Javier González
2020-07-03 5:20 ` Damien Le Moal
2020-07-03 6:28 ` Javier González
2020-07-03 8:35 ` Damien Le Moal
2020-07-02 6:54 ` [PATCH 2/4] block: add support for zone offline transition Javier González
2020-07-02 8:10 ` Damien Le Moal
2020-07-02 8:39 ` Javier González
2020-07-02 8:52 ` Damien Le Moal
2020-07-02 6:54 ` [PATCH 3/4] nvme: Add consistency check for zone count Javier González
2020-07-02 8:16 ` Damien Le Moal [this message]
2020-07-02 8:19 ` Johannes Thumshirn
2020-07-02 8:27 ` Javier González
2020-07-02 6:54 ` [PATCH 4/4] block: add attributes to zone report Javier González
2020-07-02 8:27 ` Damien Le Moal
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=CY4PR04MB3751A70BE6C1EA7DC930C9C3E76D0@CY4PR04MB3751.namprd04.prod.outlook.com \
--to=damien.lemoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=javier.gonz@samsung.com \
--cc=javier@javigon.com \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mb@lightnvm.io \
--cc=nj.shetty@samsung.com \
--cc=sagi@grimberg.me \
--cc=selvakuma.s1@samsung.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;
as well as URLs for NNTP newsgroup(s).