tree 7f0c54bb284f58019f30e78603a3ec3ecf813f19
parent eb89a6287d27d90f10cf7b80da4a5dbd9d1bcd3e
author Darrick J. Wong <darrick.wong@oracle.com> 1406334912 -0700
committer Theodore Ts'o <tytso@mit.edu> 1406504531 -0400

e2fsck: clear badblocks inode when checksum fails

If the badblocks inode fails checksum verification, just clear the
inode and move on.  If we don't do this, we can end up importing a lot
of garbage into the badblocks list, which will then cause fsck to try
to regenerate anything that was sitting atop the supposedly damaged
blocks.  Given that most hardware will remap bad sectors transparently
from ext4, the number of people this could affect adversely is pretty
low.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>