[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5d47c76d-5b7c-456a-99cc-1c443cdf8b67@suse.de>
Date: Tue, 27 May 2025 08:21:29 +0200
From: Hannes Reinecke <hare@...e.de>
To: Yu Kuai <yukuai1@...weicloud.com>, hch@....de, xni@...hat.com,
colyli@...nel.org, song@...nel.org, yukuai3@...wei.com
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-raid@...r.kernel.org, yi.zhang@...wei.com, yangerkun@...wei.com,
johnny.chenyi@...wei.com
Subject: Re: [PATCH 13/23] md/md-bitmap: fix dm-raid max_write_behind setting
On 5/24/25 08:13, Yu Kuai wrote:
> From: Yu Kuai <yukuai3@...wei.com>
>
> It's supposed to be COUNTER_MAX / 2, not COUNTER_MAX.
>
> Signed-off-by: Yu Kuai <yukuai3@...wei.com>
> ---
> drivers/md/md-bitmap.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/md/md-bitmap.c b/drivers/md/md-bitmap.c
> index 689d5dba9328..535bc1888e8c 100644
> --- a/drivers/md/md-bitmap.c
> +++ b/drivers/md/md-bitmap.c
> @@ -777,7 +777,7 @@ static int md_bitmap_new_disk_sb(struct bitmap *bitmap)
> * is a good choice? We choose COUNTER_MAX / 2 arbitrarily.
> */
> write_behind = bitmap->mddev->bitmap_info.max_write_behind;
> - if (write_behind > COUNTER_MAX)
> + if (write_behind > COUNTER_MAX / 2)
> write_behind = COUNTER_MAX / 2;
> sb->write_behind = cpu_to_le32(write_behind);
> bitmap->mddev->bitmap_info.max_write_behind = write_behind;
Reviewed-by: Hannes Reinecke <hare@...e.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@...e.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
Powered by blists - more mailing lists