From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Dennis Maisenbacher <Dennis.Maisenbacher@wdc.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: Niklas Cassel <niklas.cassel@wdc.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Damien Le Moal <damien.lemoal@wdc.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] nvmet: fix mar and mor off-by-one errors
Date: Wed, 7 Sep 2022 07:35:04 +0900 [thread overview]
Message-ID: <8154fb0a-4cda-a4bc-29ef-8435a3edb264@opensource.wdc.com> (raw)
In-Reply-To: <d3b4ef13-62fc-1bf4-3a5d-3cc740df82b8@nvidia.com>
On 9/7/22 06:53, Chaitanya Kulkarni wrote:
> On 9/6/22 00:39, Dennis Maisenbacher wrote:
>> From: Dennis Maisenbacher <dennis.maisenbacher@wdc.com>
>>
>> Maximum Active Resources (MAR) and Maximum Open Resources (MOR) are 0's
>> based vales where a value of 0xffffffff indicates that there is no limit.
>>
>> Decrement the values that are returned by bdev_max_open_zones and
>> bdev_max_active_zones as the block layer helpers are not 0's based.
>> A 0 returned by the block layer helpers indicates no limit, thus convert
>> it to 0xffffffff (U32_MAX).
>>
>> Fixes: aaf2e048af27 ("nvmet: add ZBD over ZNS backend support")
>> Suggested-by: Niklas Cassel <niklas.cassel@wdc.com>
>> Signed-off-by: Dennis Maisenbacher <dennis.maisenbacher@wdc.com>
>> ---
>> Changes in v2:
>> - Add explicit check if block layer helpers return a 0 and if so
>> convert it to U32_MAX.
>> - Add Fixes tag.
>>
>> drivers/nvme/target/zns.c | 17 +++++++++++++++--
>> 1 file changed, 15 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/nvme/target/zns.c b/drivers/nvme/target/zns.c
>> index c7ef69f29fe4..eae81f939067 100644
>> --- a/drivers/nvme/target/zns.c
>> +++ b/drivers/nvme/target/zns.c
>> @@ -100,6 +100,7 @@ void nvmet_execute_identify_cns_cs_ns(struct nvmet_req *req)
>> struct nvme_id_ns_zns *id_zns;
>> u64 zsze;
>> u16 status;
>> + u32 mar, mor;
>
> consider :-
> + u32 mar, mor;
> u64 zsze;
> u16 status;
>
>>
>> if (le32_to_cpu(req->cmd->identify.nsid) == NVME_NSID_ALL) {
>> req->error_loc = offsetof(struct nvme_identify, nsid);
>> @@ -130,8 +131,20 @@ void nvmet_execute_identify_cns_cs_ns(struct nvmet_req *req)
>> zsze = (bdev_zone_sectors(req->ns->bdev) << 9) >>
>> req->ns->blksize_shift;
>> id_zns->lbafe[0].zsze = cpu_to_le64(zsze);
>> - id_zns->mor = cpu_to_le32(bdev_max_open_zones(req->ns->bdev));
>> - id_zns->mar = cpu_to_le32(bdev_max_active_zones(req->ns->bdev));
>> +
>> + mor = bdev_max_open_zones(req->ns->bdev);
>> + if (!mor)
>> + mor = U32_MAX;
>> + else
>> + --mor;
>> + id_zns->mor = cpu_to_le32(mor);
>> +
>> + mar = bdev_max_active_zones(req->ns->bdev);
>> + if (!mar)
>> + mar = U32_MAX;
>> + else
>> + --mar;
>> + id_zns->mar = cpu_to_le32(mar);
>>
>
> above 14 lines of code can be simplified as in 4-5 lines :-
Simplified ? It is much harder to read in my opinion...
>
> mor = bdev_max_open_zones(req->ns->bdev);
> id->zns->mor = cpu_tp_le32(mor ? mor - 1 : U32_MAX);
>
> mar = bdev_max_active_zones(req->ns->bdev);
> id->zns->mar = cpu_tp_le32(mar ? mar - 1 : U32_MAX);
>
>> done:
>> status = nvmet_copy_to_sgl(req, 0, id_zns, sizeof(*id_zns));
>
>
> either way,
>
> Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-09-06 22:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 7:39 Dennis Maisenbacher
2022-09-06 21:53 ` Chaitanya Kulkarni
2022-09-06 22:35 ` Damien Le Moal [this message]
2022-09-07 2:43 ` Chaitanya Kulkarni
2022-09-07 7:04 ` Dennis Maisenbacher
2022-09-07 6:39 ` 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=8154fb0a-4cda-a4bc-29ef-8435a3edb264@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=Dennis.Maisenbacher@wdc.com \
--cc=chaitanyak@nvidia.com \
--cc=damien.lemoal@wdc.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=niklas.cassel@wdc.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
all inboxes | Powered by JetHome®