From: Niklas Cassel <cassel@kernel.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Subject: Re: [PATCH] null_blk: Print correct max open zones limit in null_init_zoned_dev()
Date: Tue, 28 May 2024 08:54:30 +0200 [thread overview]
Message-ID: <ZlV_ppTeuvoIrxGt@ryzen.lan> (raw)
In-Reply-To: <20240528062852.437599-1-dlemoal@kernel.org>
On Tue, May 28, 2024 at 03:28:52PM +0900, Damien Le Moal wrote:
> When changing the maximum number of open zones, print that number
> instead of the total number of zones.
>
> Fixes: dc4d137ee3b7 ("null_blk: add support for max open/active zone limit for zoned devices")
> Cc: stable@vger.kernel.org
> Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
> ---
> drivers/block/null_blk/zoned.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/block/null_blk/zoned.c b/drivers/block/null_blk/zoned.c
> index 5b5a63adacc1..79c8e5e99f7f 100644
> --- a/drivers/block/null_blk/zoned.c
> +++ b/drivers/block/null_blk/zoned.c
> @@ -108,7 +108,7 @@ int null_init_zoned_dev(struct nullb_device *dev,
> if (dev->zone_max_active && dev->zone_max_open > dev->zone_max_active) {
> dev->zone_max_open = dev->zone_max_active;
> pr_info("changed the maximum number of open zones to %u\n",
> - dev->nr_zones);
> + dev->zone_max_open);
> } else if (dev->zone_max_open >= dev->nr_zones - dev->zone_nr_conv) {
> dev->zone_max_open = 0;
> pr_info("zone_max_open limit disabled, limit >= zone count\n");
> --
> 2.45.1
>
Reviewed-by: Niklas Cassel <cassel@kernel.org>
next prev parent reply other threads:[~2024-05-28 6:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 6:28 [PATCH] null_blk: Print correct max open zones limit in null_init_zoned_dev() Damien Le Moal
2024-05-28 6:54 ` Niklas Cassel [this message]
2024-05-28 12:57 ` Jens Axboe
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=ZlV_ppTeuvoIrxGt@ryzen.lan \
--to=cassel@kernel.org \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=linux-block@vger.kernel.org \
/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