From: Chao Yu <chao@kernel.org>
To: Hongbo Li <lihongbo22@huawei.com>, jaegeuk@kernel.org
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, sandeen@redhat.com
Subject: Re: [PATCH v5 0/7] f2fs: new mount API conversion
Date: Mon, 14 Jul 2025 10:27:24 +0800 [thread overview]
Message-ID: <b12d791e-a9f6-4b9d-a299-858821ebc1b5@kernel.org> (raw)
In-Reply-To: <20250710121415.628398-1-lihongbo22@huawei.com>
On 7/10/25 20:14, Hongbo Li wrote:
> In this version, we have finished the issues pointed in v4.
> First, I'd like to express my sincere thanks to Jaegeuk and Chao
> for reviewing this patch series and providing corrections. I also
> appreciate Eric for rebasing the patches onto the latest branch to
> ensure forward compatibility.
>
> The latest patch series has addressed all the issues mentioned in
> the previous set. For modified patches, I've re-added Signed-off-by
> tags (SOB) and uniformly removed all Reviewed-by tags.
>
> v5:
> - Add check for bggc_mode(off) with sb blkzone case.
> - Fix the 0day-ci robot reports.
Looks good to me, feel free to add to all patches:
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
>
> v4: https://lore.kernel.org/all/20250602090224.485077-1-lihongbo22@huawei.com/
> - Change is_remount as bool type in patch 2.
> - Remove the warning reported by Dan for patch 5.
> - Enhance sanity check and fix some coding style suggested by
> Jaegeuk in patch 5.
> - Change the log info when compression option conflicts in patch 5.
> - Fix the issues reported by code-reviewing in patch 5.
> - Context modified in patch 7.
>
> V3: https://lore.kernel.org/all/20250423170926.76007-1-sandeen@redhat.com/
> - Rebase onto git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git
> dev branch
> - Fix up some 0day robot warnings
>
> (Here is the origianl cover letter:)
>
> Since many filesystems have done the new mount API conversion,
> we introduce the new mount API conversion in f2fs.
>
> The series can be applied on top of the current mainline tree
> and the work is based on the patches from Lukas Czerner (has
> done this in ext4[1]). His patch give me a lot of ideas.
>
> Here is a high level description of the patchset:
>
> 1. Prepare the f2fs mount parameters required by the new mount
> API and use it for parsing, while still using the old API to
> get mount options string. Split the parameter parsing and
> validation of the parse_options helper into two separate
> helpers.
>
> f2fs: Add fs parameter specifications for mount options
> f2fs: move the option parser into handle_mount_opt
>
> 2. Remove the use of sb/sbi structure of f2fs from all the
> parsing code, because with the new mount API the parsing is
> going to be done before we even get the super block. In this
> part, we introduce f2fs_fs_context to hold the temporary
> options when parsing. For the simple options check, it has
> to be done during parsing by using f2fs_fs_context structure.
> For the check which needs sb/sbi, we do this during super
> block filling.
>
> f2fs: Allow sbi to be NULL in f2fs_printk
> f2fs: Add f2fs_fs_context to record the mount options
> f2fs: separate the options parsing and options checking
>
> 3. Switch the f2fs to use the new mount API for mount and
> remount.
>
> f2fs: introduce fs_context_operation structure
> f2fs: switch to the new mount api
>
> [1] https://lore.kernel.org/all/20211021114508.21407-1-lczerner@redhat.com/
>
> Hongbo Li (7):
> f2fs: Add fs parameter specifications for mount options
> f2fs: move the option parser into handle_mount_opt
> f2fs: Allow sbi to be NULL in f2fs_printk
> f2fs: Add f2fs_fs_context to record the mount options
> f2fs: separate the options parsing and options checking
> f2fs: introduce fs_context_operation structure
> f2fs: switch to the new mount api
>
> fs/f2fs/super.c | 2101 +++++++++++++++++++++++++++--------------------
> 1 file changed, 1190 insertions(+), 911 deletions(-)
>
prev parent reply other threads:[~2025-07-14 2:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 12:14 [PATCH v5 0/7] f2fs: new mount API conversion Hongbo Li
2025-07-10 12:14 ` [PATCH v5 1/7] f2fs: Add fs parameter specifications for mount options Hongbo Li
2025-07-10 12:14 ` [PATCH v5 2/7] f2fs: move the option parser into handle_mount_opt Hongbo Li
2025-07-10 12:14 ` [PATCH v5 3/7] f2fs: Allow sbi to be NULL in f2fs_printk Hongbo Li
2025-07-10 12:14 ` [PATCH v5 4/7] f2fs: Add f2fs_fs_context to record the mount options Hongbo Li
2025-07-10 12:14 ` [PATCH v5 5/7] f2fs: separate the options parsing and options checking Hongbo Li
2025-07-10 12:14 ` [PATCH v5 6/7] f2fs: introduce fs_context_operation structure Hongbo Li
2025-07-10 12:14 ` [PATCH v5 7/7] f2fs: switch to the new mount api Hongbo Li
2025-07-10 12:18 ` [PATCH v5 0/7] f2fs: new mount API conversion Hongbo Li
2025-07-11 16:30 ` [f2fs-dev] " patchwork-bot+f2fs
2025-07-14 2:27 ` Chao Yu [this message]
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=b12d791e-a9f6-4b9d-a299-858821ebc1b5@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=lihongbo22@huawei.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@redhat.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).