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 07/13] ext4: factor out ext4_encoding_init()
Date: Wed, 31 Aug 2022 13:50:21 +0200 [thread overview]
Message-ID: <20220831115021.3xrmazefuefhzq3z@quack3> (raw)
In-Reply-To: <20220830120411.2371968-8-yanaijie@huawei.com>
On Tue 30-08-22 20:04:05, Jason Yan wrote:
> Factor out ext4_encoding_init(). No functional change.
>
> Signed-off-by: Jason Yan <yanaijie@huawei.com>
Looks good. Feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
> ---
> fs/ext4/super.c | 80 +++++++++++++++++++++++++++----------------------
> 1 file changed, 44 insertions(+), 36 deletions(-)
>
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index 458d146149b2..9ee27472b802 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -4521,6 +4521,48 @@ static int ext4_inode_info_init(struct super_block *sb,
> return 0;
> }
>
> +static int ext4_encoding_init(struct super_block *sb, struct ext4_super_block *es)
> +{
> +#if IS_ENABLED(CONFIG_UNICODE)
> + const struct ext4_sb_encodings *encoding_info;
> + struct unicode_map *encoding;
> + __u16 encoding_flags = le16_to_cpu(es->s_encoding_flags);
> +
> + if (!ext4_has_feature_casefold(sb) || sb->s_encoding)
> + return 0;
> +
> + encoding_info = ext4_sb_read_encoding(es);
> + if (!encoding_info) {
> + ext4_msg(sb, KERN_ERR,
> + "Encoding requested by superblock is unknown");
> + return -EINVAL;
> + }
> +
> + encoding = utf8_load(encoding_info->version);
> + if (IS_ERR(encoding)) {
> + ext4_msg(sb, KERN_ERR,
> + "can't mount with superblock charset: %s-%u.%u.%u "
> + "not supported by the kernel. flags: 0x%x.",
> + encoding_info->name,
> + unicode_major(encoding_info->version),
> + unicode_minor(encoding_info->version),
> + unicode_rev(encoding_info->version),
> + encoding_flags);
> + return -EINVAL;
> + }
> + ext4_msg(sb, KERN_INFO,"Using encoding defined by superblock: "
> + "%s-%u.%u.%u with flags 0x%hx", encoding_info->name,
> + unicode_major(encoding_info->version),
> + unicode_minor(encoding_info->version),
> + unicode_rev(encoding_info->version),
> + encoding_flags);
> +
> + sb->s_encoding = encoding;
> + sb->s_encoding_flags = encoding_flags;
> +#endif
> + return 0;
> +}
> +
> static int __ext4_fill_super(struct fs_context *fc, struct super_block *sb)
> {
> struct buffer_head *bh, **group_desc;
> @@ -4678,42 +4720,8 @@ static int __ext4_fill_super(struct fs_context *fc, struct super_block *sb)
>
> ext4_apply_options(fc, sb);
>
> -#if IS_ENABLED(CONFIG_UNICODE)
> - if (ext4_has_feature_casefold(sb) && !sb->s_encoding) {
> - const struct ext4_sb_encodings *encoding_info;
> - struct unicode_map *encoding;
> - __u16 encoding_flags = le16_to_cpu(es->s_encoding_flags);
> -
> - encoding_info = ext4_sb_read_encoding(es);
> - if (!encoding_info) {
> - ext4_msg(sb, KERN_ERR,
> - "Encoding requested by superblock is unknown");
> - goto failed_mount;
> - }
> -
> - encoding = utf8_load(encoding_info->version);
> - if (IS_ERR(encoding)) {
> - ext4_msg(sb, KERN_ERR,
> - "can't mount with superblock charset: %s-%u.%u.%u "
> - "not supported by the kernel. flags: 0x%x.",
> - encoding_info->name,
> - unicode_major(encoding_info->version),
> - unicode_minor(encoding_info->version),
> - unicode_rev(encoding_info->version),
> - encoding_flags);
> - goto failed_mount;
> - }
> - ext4_msg(sb, KERN_INFO,"Using encoding defined by superblock: "
> - "%s-%u.%u.%u with flags 0x%hx", encoding_info->name,
> - unicode_major(encoding_info->version),
> - unicode_minor(encoding_info->version),
> - unicode_rev(encoding_info->version),
> - encoding_flags);
> -
> - sb->s_encoding = encoding;
> - sb->s_encoding_flags = encoding_flags;
> - }
> -#endif
> + if (ext4_encoding_init(sb, es))
> + goto failed_mount;
>
> if (test_opt(sb, DATA_FLAGS) == EXT4_MOUNT_JOURNAL_DATA) {
> printk_once(KERN_WARNING "EXT4-fs: Warning: mounting with data=journal disables delayed allocation, dioread_nolock, O_DIRECT and fast_commit support!\n");
> --
> 2.31.1
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2022-08-31 11:50 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 [this message]
2022-08-30 12:04 ` [PATCH 08/13] ext4: factor out ext4_handle_csum() Jason Yan
2022-08-31 11:52 ` Jan Kara
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=20220831115021.3xrmazefuefhzq3z@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