diff options
| author | Brian Norris <computersforpeace@gmail.com> | 2011-09-20 18:35:34 -0700 |
|---|---|---|
| committer | Artem Bityutskiy <artem.bityutskiy@intel.com> | 2011-09-21 09:19:07 +0300 |
| commit | 623978de362a5faeb18d8395fa86089650642626 (patch) | |
| tree | f5f6b3b77b5a25f438f0b1b90bf591986a1fa489 /tools | |
| parent | 167a8d52509a0f7d6728a79e2588b800e866c147 (diff) | |
| download | op-kernel-dev-623978de362a5faeb18d8395fa86089650642626.zip op-kernel-dev-623978de362a5faeb18d8395fa86089650642626.tar.gz | |
mtd: nand: scrub BBT on ECC errors
Now that `read_bbt()' returns ECC error codes properly, we handle those
codes when checking the integrity of our flash-based BBT.
The modifications can be described by this new policy:
*) On any uncorrected ECC error, we invalidate the corresponding table
and retry our version-checking integrity logic.
*) On corrected bitflips, we mark both tables for re-writing to flash
(a.k.a. scrubbing).
Current integrity checks (i.e., comparing version numbers, etc.) should
take care of all the cases that result in rescanning the device for bad
blocks or falling back to the BBT as found in the mirror descriptor.
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@intel.com>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions
