> 2023年12月24日 08:28，Coly Li <[email protected]> 写道：
>
> 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.
>
> Fixes: 3ea3354cb9f0 ("badblocks: improve badblocks_check() for multiple
> ranges handling")
> Reported-and-tested-by: Ira Weiny <[email protected]>
> Signed-off-by: Coly Li <[email protected]>
> Link:
> https://lore.kernel.org/nvdimm/[email protected]/
> Cc: Dan Williams <[email protected]>
> Cc: Geliang Tang <[email protected]>
> Cc: Hannes Reinecke <[email protected]>
> Cc: Jens Axboe <[email protected]>
> Cc: NeilBrown <[email protected]>
> Cc: Vishal L Verma <[email protected]>
> Cc: Xiao Ni <[email protected]>
> ---
> block/badblocks.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
Hi Jens,
Is it possible to take this fix into 6.7 still? Thanks in advance.
Coly Li
[snipped]
