]> git.ipfire.org Git - thirdparty/e2fsprogs.git/commit
e2fsck: always ask to fix an inode that fails checksum verification
authorDarrick J. Wong <darrick.wong@oracle.com>
Sun, 3 Aug 2014 02:52:29 +0000 (22:52 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Sun, 3 Aug 2014 02:52:29 +0000 (22:52 -0400)
commit6e3c3b755235bbae53cbb9ddfe9fd3bbd4ecc298
tree1ccda038df722324219303355703d05164f6c8a1
parentd4864e020421bf13afde4da04277ef5ca03adffd
e2fsck: always ask to fix an inode that fails checksum verification

If an inode fails checksum verification during pass 1 and the user
doesn't fix or clear the inode as part of the regular inode checks,
ensure that e2fsck remembers to ask the user if he simply wants to
correct the checksum.

We weren't capturing all the ways out of an interation of the inode
scanning loop, which means that not all errors were caught.  Also,
we might as well clear the 'failed csum' flag if we write the inode
directly from the inode scanning loop.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
e2fsck/pass1.c
tests/f_deleted_inode_bad_csum/expect.1 [new file with mode: 0644]
tests/f_deleted_inode_bad_csum/expect.2 [new file with mode: 0644]
tests/f_deleted_inode_bad_csum/image.gz [new file with mode: 0644]
tests/f_deleted_inode_bad_csum/name [new file with mode: 0644]