From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: dann frazier <dann.frazier@canonical.com>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
yanaijie@huawei.com, colin.king@canonical.com,
kamal.mostafa@canonical.com, ike.pan@canonical.com
Subject: Re: [Bisect] ext4_validate_inode_bitmap:98: comm stress-ng: Corrupt inode bitmap
Date: Sat, 7 Jul 2018 00:10:18 -0400 [thread overview]
Message-ID: <20180707041018.GB3546@thunk.org> (raw)
In-Reply-To: <20180706174324.GA3049@xps13.dannf>
On Fri, Jul 06, 2018 at 11:43:24AM -0600, dann frazier wrote:
> Hi,
> We're seeing a regression triggered by the stress-ng[*] "chdir" test
> that I've bisected to:
>
> 044e6e3d74a3 ext4: don't update checksum of new initialized bitmaps
>
> So far we've only seen failures on servers based on HiSilicon's family
> of ARM64 SoCs (D05/Hi1616 SoC, D06/Hi1620 SoC). On these systems it is
> very reproducible.
Thanks for the report. Can you verify whether or not this patch fixes
things for you?
- Ted
diff --git a/fs/ext4/ialloc.c b/fs/ext4/ialloc.c
index da6c10c1e37a..1cfb74bc4dca 100644
--- a/fs/ext4/ialloc.c
+++ b/fs/ext4/ialloc.c
@@ -90,6 +90,8 @@ static int ext4_validate_inode_bitmap(struct super_block *sb,
return -EFSCORRUPTED;
ext4_lock_group(sb, block_group);
+ if (buffer_verified(bh))
+ goto verified;
blk = ext4_inode_bitmap(sb, desc);
if (!ext4_inode_bitmap_csum_verify(sb, block_group, desc, bh,
EXT4_INODES_PER_GROUP(sb) / 8)) {
@@ -101,6 +103,7 @@ static int ext4_validate_inode_bitmap(struct super_block *sb,
return -EFSBADCRC;
}
set_buffer_verified(bh);
+verified:
ext4_unlock_group(sb, block_group);
return 0;
}
next prev parent reply other threads:[~2018-07-07 4:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 17:43 [Bisect] ext4_validate_inode_bitmap:98: comm stress-ng: Corrupt inode bitmap dann frazier
2018-07-07 4:10 ` Theodore Y. Ts'o [this message]
2018-07-10 16:51 ` dann frazier
2018-07-10 20:43 ` dann frazier
2018-07-11 8:57 ` Ike Panhc
2018-07-12 23:08 ` Theodore Y. Ts'o
2018-07-14 11:21 ` dann frazier
2018-07-16 23:13 ` dann frazier
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=20180707041018.GB3546@thunk.org \
--to=tytso@mit.edu \
--cc=colin.king@canonical.com \
--cc=dann.frazier@canonical.com \
--cc=ike.pan@canonical.com \
--cc=kamal.mostafa@canonical.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yanaijie@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).