From: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
To: Jason Yan <yanaijie@huawei.com>
Cc: tytso@mit.edu, adilger.kernel@dilger.ca, jack@suse.cz,
lczerner@redhat.com, linux-ext4@vger.kernel.org
Subject: Re: [PATCH v2 01/13] ext4: goto right label 'failed_mount3a'
Date: Thu, 8 Sep 2022 14:09:22 +0530 [thread overview]
Message-ID: <20220908083922.cbwpwp7lmr3wqco3@riteshh-domain> (raw)
In-Reply-To: <20220903030156.770313-2-yanaijie@huawei.com>
On 22/09/03 11:01AM, Jason Yan wrote:
> Before these two branches neither loaded the journal nor created the
> xattr cache. So the right label to goto is 'failed_mount3a'. Although
> this did not cause any issues because the error handler validated if the
> pointer is null. However this still made me confused when reading
> the code. So it's still worth to modify to goto the right label.
>
> Signed-off-by: Jason Yan <yanaijie@huawei.com>
> Reviewed-by: Jan Kara <jack@suse.cz>
> ---
> fs/ext4/super.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
This looks good to me.
Reviewed-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
>
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index 9a66abcca1a8..6126da867b26 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -5079,30 +5079,30 @@ static int __ext4_fill_super(struct fs_context *fc, struct super_block *sb)
> ext4_has_feature_journal_needs_recovery(sb)) {
> ext4_msg(sb, KERN_ERR, "required journal recovery "
> "suppressed and not mounted read-only");
> - goto failed_mount_wq;
> + goto failed_mount3a;
> } else {
> /* Nojournal mode, all journal mount options are illegal */
> if (test_opt2(sb, EXPLICIT_JOURNAL_CHECKSUM)) {
> ext4_msg(sb, KERN_ERR, "can't mount with "
> "journal_checksum, fs mounted w/o journal");
> - goto failed_mount_wq;
> + goto failed_mount3a;
> }
> if (test_opt(sb, JOURNAL_ASYNC_COMMIT)) {
> ext4_msg(sb, KERN_ERR, "can't mount with "
> "journal_async_commit, fs mounted w/o journal");
> - goto failed_mount_wq;
> + goto failed_mount3a;
> }
> if (sbi->s_commit_interval != JBD2_DEFAULT_MAX_COMMIT_AGE*HZ) {
> ext4_msg(sb, KERN_ERR, "can't mount with "
> "commit=%lu, fs mounted w/o journal",
> sbi->s_commit_interval / HZ);
> - goto failed_mount_wq;
> + goto failed_mount3a;
> }
> if (EXT4_MOUNT_DATA_FLAGS &
> (sbi->s_mount_opt ^ sbi->s_def_mount_opt)) {
> ext4_msg(sb, KERN_ERR, "can't mount with "
> "data=, fs mounted w/o journal");
> - goto failed_mount_wq;
> + goto failed_mount3a;
> }
> sbi->s_def_mount_opt &= ~EXT4_MOUNT_JOURNAL_CHECKSUM;
> clear_opt(sb, JOURNAL_CHECKSUM);
> --
> 2.31.1
>
next prev parent reply other threads:[~2022-09-08 8:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 3:01 [PATCH v2 00/13] some refactor of __ext4_fill_super() Jason Yan
2022-09-03 3:01 ` [PATCH v2 01/13] ext4: goto right label 'failed_mount3a' Jason Yan
2022-09-08 8:39 ` Ritesh Harjani (IBM) [this message]
2022-09-03 3:01 ` [PATCH v2 02/13] ext4: remove cantfind_ext4 error handler Jason Yan
2022-09-08 8:40 ` Ritesh Harjani (IBM)
2022-09-03 3:01 ` [PATCH v2 03/13] ext4: factor out ext4_set_def_opts() Jason Yan
2022-09-08 8:44 ` Ritesh Harjani (IBM)
2022-09-12 2:20 ` Jason Yan
2022-09-03 3:01 ` [PATCH v2 04/13] ext4: factor out ext4_handle_clustersize() Jason Yan
2022-09-08 8:45 ` Ritesh Harjani (IBM)
2022-09-03 3:01 ` [PATCH v2 05/13] ext4: factor out ext4_fast_commit_init() Jason Yan
2022-09-08 8:45 ` Ritesh Harjani (IBM)
2022-09-03 3:01 ` [PATCH v2 06/13] ext4: factor out ext4_inode_info_init() Jason Yan
2022-09-08 8:46 ` Ritesh Harjani (IBM)
2022-09-03 3:01 ` [PATCH v2 07/13] ext4: factor out ext4_encoding_init() Jason Yan
2022-09-08 8:56 ` Ritesh Harjani (IBM)
2022-09-12 2:30 ` Jason Yan
2022-09-12 3:12 ` Jason Yan
2022-09-03 3:01 ` [PATCH v2 08/13] ext4: factor out ext4_init_metadata_csum() Jason Yan
2022-09-08 8:57 ` Ritesh Harjani (IBM)
2022-09-03 3:01 ` [PATCH v2 09/13] ext4: factor out ext4_check_feature_compatibility() Jason Yan
2022-09-08 8:58 ` Ritesh Harjani (IBM)
2022-09-03 3:01 ` [PATCH v2 10/13] ext4: factor out ext4_geometry_check() Jason Yan
2022-09-08 9:00 ` Ritesh Harjani (IBM)
2022-09-03 3:01 ` [PATCH v2 11/13] ext4: factor out ext4_group_desc_init() and ext4_group_desc_free() Jason Yan
2022-09-08 9:03 ` Ritesh Harjani (IBM)
2022-09-03 3:01 ` [PATCH v2 12/13] ext4: factor out ext4_load_and_init_journal() Jason Yan
2022-09-08 9:04 ` Ritesh Harjani (IBM)
2022-09-03 3:01 ` [PATCH v2 13/13] ext4: factor out ext4_journal_data_mode_check() Jason Yan
2022-09-08 9:06 ` Ritesh Harjani (IBM)
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=20220908083922.cbwpwp7lmr3wqco3@riteshh-domain \
--to=ritesh.list@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--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).