We find a checksum error and a inode corruption problem while doing stress test, this 4 patches address to fix them. The first patch is relate to the error simulation, and the second & third patch are prepare to do the fix. The last patch fix these two issue. - Checksum error EXT4-fs error (device sda): ext4_lookup:1784: inode #131074: comm cat: iget: checksum invalid - Inode corruption e2fsck 1.46.0 (29-Jan-2020) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Entry 'foo' in / (2) has deleted/unused inode 17. Clear<y>? yes Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Inode bitmap differences: -17 Fix<y>? yes Free inodes count wrong for group #0 (32750, counted=32751). Fix<y>? yes Free inodes count wrong (32750, counted=32751). Fix<y>? yes Change since v1: - Add a patch to prevent ext4_do_update_inode() return before filling the inode buffer. - Do not use BH_New flag to indicate the empty buffer, postpone the zero and uptodate logic into ext4_do_update_inode() before filling the inode buffer. Thanks, Yi. Zhang Yi (4): ext4: move inode eio simulation behind io completeion ext4: remove an unnecessary if statement in __ext4_get_inode_loc() ext4: don't return error if huge_file feature mismatch ext4: prevent getting empty inode buffer fs/ext4/inode.c | 206 +++++++++++++++++++++++++----------------------- 1 file changed, 109 insertions(+), 97 deletions(-) -- 2.31.1