在 2025/2/21 18:09, Zhu Yanjun 写道:
On 21.02.25 09:11, Zheng Qixing wrote:
From: Li Nan <[email protected]>
The number of badblocks cannot exceed MAX_BADBLOCKS, but it should be
allowed to equal MAX_BADBLOCKS.
Fixes: aa511ff8218b ("badblocks: switch to the improved badblock handling
code")
Signed-off-by: Li Nan <[email protected]>
---
block/badblocks.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/block/badblocks.c b/block/badblocks.c
index a953d2e9417f..87267bae6836 100644
--- a/block/badblocks.c
+++ b/block/badblocks.c
@@ -700,7 +700,7 @@ static bool can_front_overwrite(struct badblocks *bb,
int prev,
*extra = 2;
}
- if ((bb->count + (*extra)) >= MAX_BADBLOCKS)
+ if ((bb->count + (*extra)) > MAX_BADBLOCKS)
return false;
In this commit,
commit c3c6a86e9efc5da5964260c322fe07feca6df782
Author: Coly Li <[email protected]>
Date: Sat Aug 12 01:05:08 2023 +0800
badblocks: add helper routines for badblock ranges handling
This patch adds several helper routines to improve badblock ranges
handling. These helper routines will be used later in the improved
version of badblocks_set()/badblocks_clear()/badblocks_check().
- Helpers prev_by_hint() and prev_badblocks() are used to find the bad
range from bad table which the searching range starts at or after.
The above is changed to MAX_BADBLOCKS. Thus, perhaps, the Fixes tag should
include the above commit?
Except that, I am fine with this commit.
Reviewed-by: Zhu Yanjun <[email protected]>
Zhu Yanjun
Thank! I will bring this fix tag in v2.
--
Thanks,
Nan
