From: Jan Kara <jack@suse.cz>
To: Jason Yan <yanaijie@huawei.com>
Cc: tytso@mit.edu, adilger.kernel@dilger.ca, jack@suse.cz,
ritesh.list@gmail.com, lczerner@redhat.com,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH 08/13] ext4: factor out ext4_handle_csum()
Date: Wed, 31 Aug 2022 13:52:39 +0200 [thread overview]
Message-ID: <20220831115239.g4br24j2fi4e2k4x@quack3> (raw)
In-Reply-To: <20220830120411.2371968-9-yanaijie@huawei.com>
On Tue 30-08-22 20:04:06, Jason Yan wrote:
> Factor out ext4_handle_csum(). No functional change.
>
> Signed-off-by: Jason Yan <yanaijie@huawei.com>
> ---
> fs/ext4/super.c | 83 +++++++++++++++++++++++++++----------------------
> 1 file changed, 46 insertions(+), 37 deletions(-)
>
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index 9ee27472b802..96cf23787bba 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -4563,6 +4563,50 @@ static int ext4_encoding_init(struct super_block *sb, struct ext4_super_block *e
> return 0;
> }
>
> +static int ext4_handle_csum(struct super_block *sb, struct ext4_super_block *es)
I'd rather call this function like ext4_init_metadata_csum().
ext4_handle_csum() seems to vague to me.
Otherwise the patch looks good to me. Feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> +{
> + struct ext4_sb_info *sbi = EXT4_SB(sb);
> +
> + /* Warn if metadata_csum and gdt_csum are both set. */
> + if (ext4_has_feature_metadata_csum(sb) &&
> + ext4_has_feature_gdt_csum(sb))
> + ext4_warning(sb, "metadata_csum and uninit_bg are "
> + "redundant flags; please run fsck.");
> +
> + /* Check for a known checksum algorithm */
> + if (!ext4_verify_csum_type(sb, es)) {
> + ext4_msg(sb, KERN_ERR, "VFS: Found ext4 filesystem with "
> + "unknown checksum algorithm.");
> + return -EINVAL;
> + }
> + ext4_setup_csum_trigger(sb, EXT4_JTR_ORPHAN_FILE,
> + ext4_orphan_file_block_trigger);
> +
> + /* Load the checksum driver */
> + sbi->s_chksum_driver = crypto_alloc_shash("crc32c", 0, 0);
> + if (IS_ERR(sbi->s_chksum_driver)) {
> + int ret = PTR_ERR(sbi->s_chksum_driver);
> + ext4_msg(sb, KERN_ERR, "Cannot load crc32c driver.");
> + sbi->s_chksum_driver = NULL;
> + return ret;
> + }
> +
> + /* Check superblock checksum */
> + if (!ext4_superblock_csum_verify(sb, es)) {
> + ext4_msg(sb, KERN_ERR, "VFS: Found ext4 filesystem with "
> + "invalid superblock checksum. Run e2fsck?");
> + return -EFSBADCRC;
> + }
> +
> + /* Precompute checksum seed for all metadata */
> + if (ext4_has_feature_csum_seed(sb))
> + sbi->s_csum_seed = le32_to_cpu(es->s_checksum_seed);
> + else if (ext4_has_metadata_csum(sb) || ext4_has_feature_ea_inode(sb))
> + sbi->s_csum_seed = ext4_chksum(sbi, ~0, es->s_uuid,
> + sizeof(es->s_uuid));
> + return 0;
> +}
> +
> static int __ext4_fill_super(struct fs_context *fc, struct super_block *sb)
> {
> struct buffer_head *bh, **group_desc;
> @@ -4632,44 +4676,9 @@ static int __ext4_fill_super(struct fs_context *fc, struct super_block *sb)
>
> sbi->s_kbytes_written = le64_to_cpu(es->s_kbytes_written);
>
> - /* Warn if metadata_csum and gdt_csum are both set. */
> - if (ext4_has_feature_metadata_csum(sb) &&
> - ext4_has_feature_gdt_csum(sb))
> - ext4_warning(sb, "metadata_csum and uninit_bg are "
> - "redundant flags; please run fsck.");
> -
> - /* Check for a known checksum algorithm */
> - if (!ext4_verify_csum_type(sb, es)) {
> - ext4_msg(sb, KERN_ERR, "VFS: Found ext4 filesystem with "
> - "unknown checksum algorithm.");
> - goto failed_mount;
> - }
> - ext4_setup_csum_trigger(sb, EXT4_JTR_ORPHAN_FILE,
> - ext4_orphan_file_block_trigger);
> -
> - /* Load the checksum driver */
> - sbi->s_chksum_driver = crypto_alloc_shash("crc32c", 0, 0);
> - if (IS_ERR(sbi->s_chksum_driver)) {
> - ext4_msg(sb, KERN_ERR, "Cannot load crc32c driver.");
> - ret = PTR_ERR(sbi->s_chksum_driver);
> - sbi->s_chksum_driver = NULL;
> - goto failed_mount;
> - }
> -
> - /* Check superblock checksum */
> - if (!ext4_superblock_csum_verify(sb, es)) {
> - ext4_msg(sb, KERN_ERR, "VFS: Found ext4 filesystem with "
> - "invalid superblock checksum. Run e2fsck?");
> - ret = -EFSBADCRC;
> + err = ext4_handle_csum(sb, es);
> + if (err)
> goto failed_mount;
> - }
> -
> - /* Precompute checksum seed for all metadata */
> - if (ext4_has_feature_csum_seed(sb))
> - sbi->s_csum_seed = le32_to_cpu(es->s_checksum_seed);
> - else if (ext4_has_metadata_csum(sb) || ext4_has_feature_ea_inode(sb))
> - sbi->s_csum_seed = ext4_chksum(sbi, ~0, es->s_uuid,
> - sizeof(es->s_uuid));
>
> ext4_set_def_opts(sb, es);
>
> --
> 2.31.1
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2022-08-31 11:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 12:03 [PATCH 00/13] some refactor of __ext4_fill_super() Jason Yan
2022-08-30 12:03 ` [PATCH 01/13] ext4: goto right label 'failed_mount3a' Jason Yan
2022-08-31 11:36 ` Jan Kara
2022-08-30 12:04 ` [PATCH 02/13] ext4: remove cantfind_ext4 error handler Jason Yan
2022-08-31 11:41 ` Jan Kara
2022-09-01 7:42 ` Jason Yan
2022-08-30 12:04 ` [PATCH 03/13] ext4: factor out ext4_set_def_opts() Jason Yan
2022-08-31 11:44 ` Jan Kara
2022-08-30 12:04 ` [PATCH 04/13] ext4: factor out ext4_handle_clustersize() Jason Yan
2022-08-31 11:46 ` Jan Kara
2022-08-30 12:04 ` [PATCH 05/13] ext4: factor out ext4_fast_commit_init() Jason Yan
2022-08-31 11:47 ` Jan Kara
2022-08-30 12:04 ` [PATCH 06/13] ext4: factor out ext4_inode_info_init() Jason Yan
2022-08-31 11:49 ` Jan Kara
2022-08-30 12:04 ` [PATCH 07/13] ext4: factor out ext4_encoding_init() Jason Yan
2022-08-31 11:50 ` Jan Kara
2022-08-30 12:04 ` [PATCH 08/13] ext4: factor out ext4_handle_csum() Jason Yan
2022-08-31 11:52 ` Jan Kara [this message]
2022-09-01 7:56 ` Jason Yan
2022-08-30 12:04 ` [PATCH 09/13] ext4: factor out ext4_compat_feature_check() Jason Yan
2022-08-31 11:55 ` Jan Kara
2022-09-01 7:58 ` Jason Yan
2022-08-30 12:04 ` [PATCH 10/13] ext4: factor out ext4_geometry_check() Jason Yan
2022-08-31 11:57 ` Jan Kara
2022-08-30 12:04 ` [PATCH 11/13] ext4: factor out ext4_group_desc_init() and ext4_group_desc_free() Jason Yan
2022-08-31 12:00 ` Jan Kara
2022-08-30 12:04 ` [PATCH 12/13] ext4: factor out ext4_load_and_init_journal() Jason Yan
2022-08-31 12:05 ` Jan Kara
2022-08-30 12:04 ` [PATCH 13/13] ext4: factor out ext4_journal_data_check() Jason Yan
2022-08-31 12:06 ` Jan Kara
2022-09-01 7:59 ` Jason Yan
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=20220831115239.g4br24j2fi4e2k4x@quack3 \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
--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).