Lines Matching full:clearing

335  * Clearing a bad blocks range from the bad block table has similar idea as
337  * when the clearing range hits middle of a bad block range, the existing bad
341  * clearing bad blocks range is naming with prefix C)
343  * 1) A clearing range is not overlapped to any already set ranges in bad block
353  * 2) The clearing range hits middle of an already setting bad blocks range in
366  * 3) The clearing range starts exactly at same LBA as an already set bad block range
390  * 4) The clearing range exactly ends at same LBA as an already set bad block
404  * 5) The clearing range is partially overlapped with an already set bad block
406  * 5.1) The already set bad block range is front overlapped with the clearing
414  *   For such situation, the clearing range C can be treated as two parts. The
425  * 5.2) The already set bad block range is behind overlaopped with the clearing
433  *   For such situation, the clearing range C can be treated as two parts. The
442  *   Now the first part clearing range C1 can be handled as condition 4), and
443  *   the second part clearing range C2 can be handled as condition 1) in next
446  *   All bad blocks range clearing can be simplified into the above 5 situations
447  *   by only handling the head part of the clearing range in each run of the
1068  * with the clearing range. The return value is how many sectors from an
1070  * covered by the clearing range and fully cleared, 'delete' is set as 1 for
1112  * Handle the condition that the clearing range hits middle of an already set
1153 		/* When clearing we round the start up and the end down.  in _badblocks_clear()