Skip to content

Commit 4872026

Browse files
YuKuai-huaweismb49
authored andcommitted
md/md-bitmap: fix dm-raid max_write_behind setting
BugLink: https://bugs.launchpad.net/bugs/2121266 [ Upstream commit 2afe17794cfed5f80295b1b9facd66e6f65e5002 ] It's supposed to be COUNTER_MAX / 2, not COUNTER_MAX. Link: https://lore.kernel.org/linux-raid/20250524061320.370630-14-yukuai1@huaweicloud.com Signed-off-by: Yu Kuai <yukuai3@huawei.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Hannes Reinecke <hare@suse.de> Signed-off-by: Sasha Levin <sashal@kernel.org> Signed-off-by: Noah Wager <noah.wager@canonical.com> Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
1 parent 9180787 commit 4872026

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

drivers/md/md-bitmap.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -787,7 +787,7 @@ static int md_bitmap_new_disk_sb(struct bitmap *bitmap)
787787
* is a good choice? We choose COUNTER_MAX / 2 arbitrarily.
788788
*/
789789
write_behind = bitmap->mddev->bitmap_info.max_write_behind;
790-
if (write_behind > COUNTER_MAX)
790+
if (write_behind > COUNTER_MAX / 2)
791791
write_behind = COUNTER_MAX / 2;
792792
sb->write_behind = cpu_to_le32(write_behind);
793793
bitmap->mddev->bitmap_info.max_write_behind = write_behind;

0 commit comments

Comments
 (0)