On Sun, 24 Dec 2023 08:28:20 +0800, Coly Li wrote:
> If prev_badblocks() returns '-1', it means no valid badblocks record
> before the checking range. It doesn't make sense to check whether
> the input checking range is overlapped with the non-existed invalid
> front range.
>
> This patch checkes whether 'prev >= 0' is true before calling
> overlap_front(), to void such invalid operations.
>
> [...]
Applied, thanks!
[1/1] badblocks: avoid checking invalid range in badblocks_check()
commit: 146e843f6b09271233c021b1677e561b7dc16303
Best regards,
--
Jens Axboe
