From: "Darrick J. Wong" <djwong@kernel.org>
To: Baokun Li <libaokun1@huawei.com>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu,
adilger.kernel@dilger.ca, jack@suse.cz, ritesh.list@gmail.com,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com,
yukuai3@huawei.com
Subject: Re: [PATCH] ext4: fix bad checksum after online resize
Date: Fri, 4 Nov 2022 08:58:16 -0700 [thread overview]
Message-ID: <Y2U2mNnUuOsbh5QG@magnolia> (raw)
In-Reply-To: <20221104083553.581928-1-libaokun1@huawei.com>
On Fri, Nov 04, 2022 at 04:35:53PM +0800, Baokun Li wrote:
> When online resizing is performed twice consecutively, the error message
> "Superblock checksum does not match superblock" is displayed for the
> second time. Here's the reproducer:
>
> mkfs.ext4 -F /dev/sdb 100M
> mount /dev/sdb /tmp/test
> resize2fs /dev/sdb 5G
> resize2fs /dev/sdb 6G
>
> To solve this issue, we moved the update of the checksum after the
> es->s_overhead_clusters is updated.
>
> Fixes: 026d0d27c488 ("ext4: reduce computation of overhead during resize")
> Fixes: de394a86658f ("ext4: update s_overhead_clusters in the superblock during an on-line resize")
> Signed-off-by: Baokun Li <libaokun1@huawei.com>
Yep, that looks correct. Sort of a pity that the checksum computation
isn't quite as automatic as it is in other filesystems, but that's my
fault... :/
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> fs/ext4/resize.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ext4/resize.c b/fs/ext4/resize.c
> index 6dfe9ccae0c5..32fbfc173571 100644
> --- a/fs/ext4/resize.c
> +++ b/fs/ext4/resize.c
> @@ -1471,8 +1471,6 @@ static void ext4_update_super(struct super_block *sb,
> * active. */
> ext4_r_blocks_count_set(es, ext4_r_blocks_count(es) +
> reserved_blocks);
> - ext4_superblock_csum_set(sb);
> - unlock_buffer(sbi->s_sbh);
>
> /* Update the free space counts */
> percpu_counter_add(&sbi->s_freeclusters_counter,
> @@ -1508,6 +1506,8 @@ static void ext4_update_super(struct super_block *sb,
> ext4_calculate_overhead(sb);
> es->s_overhead_clusters = cpu_to_le32(sbi->s_overhead);
>
> + ext4_superblock_csum_set(sb);
> + unlock_buffer(sbi->s_sbh);
> if (test_opt(sb, DEBUG))
> printk(KERN_DEBUG "EXT4-fs: added group %u:"
> "%llu blocks(%llu free %llu reserved)\n", flex_gd->count,
> --
> 2.31.1
>
next prev parent reply other threads:[~2022-11-04 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 8:35 [PATCH] ext4: fix bad checksum after online resize Baokun Li
2022-11-04 15:58 ` Darrick J. Wong [this message]
2022-11-07 13:03 ` 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=Y2U2mNnUuOsbh5QG@magnolia \
--to=djwong@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=libaokun1@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
--cc=yi.zhang@huawei.com \
--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