[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210810142722.923175-1-yi.zhang@huawei.com>
Date: Tue, 10 Aug 2021 22:27:19 +0800
From: Zhang Yi <yi.zhang@...wei.com>
To: <linux-ext4@...r.kernel.org>
CC: <tytso@....edu>, <adilger.kernel@...ger.ca>, <jack@...e.cz>,
<yi.zhang@...wei.com>, <yukuai3@...wei.com>
Subject: [PATCH 0/3] ext4: fix a inode checksum error
We find a checksum error and a inode corruption problem while doing
stress test, this 3 patches address to fix them.
- 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
The first patch is relate to the error simulation, and the second patch
is just a cleanup patch, which are prepare to do the fix. The last patch
fix these two issue.
Thanks,
Yi.
Zhang Yi (3):
ext4: move inode eio simulation behind io completeion
ext4: remove an unnecessary if statement in __ext4_get_inode_loc()
ext4: prevent getting empty inode buffer
fs/ext4/inode.c | 177 +++++++++++++++++++++++++-----------------------
1 file changed, 94 insertions(+), 83 deletions(-)
--
2.31.1
Powered by blists - more mailing lists