nvmet: fix mar and mor off-by-one errors
authorDennis Maisenbacher <dennis.maisenbacher@wdc.com>
Tue, 6 Sep 2022 07:39:28 +0000 (09:39 +0200)
committerChristoph Hellwig <hch@lst.de>
Wed, 7 Sep 2022 06:33:17 +0000 (08:33 +0200)
commitb7e97872a65e1d57b4451769610554c131f37a0a
tree1bd19c543d990b0da8368e722cafc88c4ef6b7f6
parent3770a42bb8ceb856877699257a43c0585a5d2996
nvmet: fix mar and mor off-by-one errors

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>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
drivers/nvme/target/zns.c