From: Zhang Yi <yi.zhang@huawei.com>
To: <linux-ext4@vger.kernel.org>
Cc: <tytso@mit.edu>, <adilger.kernel@dilger.ca>, <jack@suse.cz>,
<yi.zhang@huawei.com>, <yukuai3@huawei.com>
Subject: [PATCH 0/3] ext4: fix a inode checksum error
Date: Tue, 10 Aug 2021 22:27:19 +0800 [thread overview]
Message-ID: <20210810142722.923175-1-yi.zhang@huawei.com> (raw)
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
next reply other threads:[~2021-08-10 14:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 14:27 Zhang Yi [this message]
2021-08-10 14:27 ` [PATCH 1/3] ext4: move inode eio simulation behind io completeion Zhang Yi
2021-08-13 12:55 ` Jan Kara
2021-08-10 14:27 ` [PATCH 2/3] ext4: remove an unnecessary if statement in __ext4_get_inode_loc() Zhang Yi
2021-08-13 13:00 ` Jan Kara
2021-08-10 14:27 ` [PATCH 3/3] ext4: prevent getting empty inode buffer Zhang Yi
2021-08-13 13:44 ` Jan Kara
2021-08-16 14:29 ` Zhang Yi
2021-08-16 17:14 ` Jan Kara
2021-08-18 12:15 ` Zhang Yi
2021-08-18 13:11 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210810142722.923175-1-yi.zhang@huawei.com \
--to=yi.zhang@huawei.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yukuai3@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).