From: Kelvin Zhang <zhangxp1998@gmail.com>
To: linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>,
Daeho Jeong <daeho43@gmail.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v8 01/11] f2fs: initialize sb_info early in f2fs_fill_super
Date: Thu, 3 Sep 2026 16:06:05 -0700 [thread overview]
Message-ID: <cd63b907d18ebef2f8dfa3c843d008c27de4ee8b.1788476500.git.zhangxp1998@gmail.com> (raw)
In-Reply-To: <cover.1788476500.git.zhangxp1998@gmail.com>
Previously, init_sb_info() was invoked late in f2fs_fill_super(), after
processing superblock error tracking, mount options, and sb->s_maxbytes.
However, read_raw_super_block() reads the superblock folio directly
from the block device mapping using folio page offsets. This makes the
initial static sb_set_blocksize(sb, F2FS_BLKSIZE) call redundant.
Move init_sb_info() to execute immediately after sbi->raw_super is
attached, allowing the block device block size to be set dynamically via
sb_set_blocksize(sb, sbi->blocksize).
This early initialization also prepares for upcoming patches that add
dynamically computed filesystem geometry fields, such as
sbi->addrs_per_block and sbi->nids_per_block, to init_sb_info(). These
fields are required by earlier initialization steps, including mount option
consistency checks and sb->s_maxbytes computation.
Signed-off-by: Kelvin Zhang <zhangxp1998@gmail.com>
---
fs/f2fs/super.c | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index 253a579e9d5b..c48acfb30a0d 100644
--- a/fs/f2fs/super.c
+++ b/fs/f2fs/super.c
@@ -5125,12 +5125,6 @@ static int f2fs_fill_super(struct super_block *sb, struct fs_context *fc)
}
mutex_init(&sbi->flush_lock);
- /* set a block size */
- if (unlikely(!sb_set_blocksize(sb, F2FS_BLKSIZE))) {
- f2fs_err(sbi, "unable to set blocksize");
- goto free_sbi;
- }
-
err = read_raw_super_block(sbi, &raw_super, &valid_super_block,
&recovery);
if (err)
@@ -5138,6 +5132,14 @@ static int f2fs_fill_super(struct super_block *sb, struct fs_context *fc)
sb->s_fs_info = sbi;
sbi->raw_super = raw_super;
+ init_sb_info(sbi);
+
+ /* set a block size */
+ if (unlikely(!sb_set_blocksize(sb, sbi->blocksize))) {
+ f2fs_err(sbi, "unable to set blocksize %u", sbi->blocksize);
+ err = -EINVAL;
+ goto free_sb_buf;
+ }
sbi->max_atc_write_bio_size = UINT_MAX;
INIT_WORK(&sbi->s_error_work, f2fs_record_error_work);
@@ -5217,8 +5219,6 @@ static int f2fs_fill_super(struct super_block *sb, struct fs_context *fc)
if (err)
goto free_bio_info;
- init_sb_info(sbi);
-
err = f2fs_init_iostat(sbi);
if (err)
goto free_bio_info;
--
2.53.0
next prev parent reply other threads:[~2026-09-03 23:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 23:06 [PATCH v8 00/11] f2fs: prepare metadata layouts for runtime block sizes Kelvin Zhang
2026-09-03 23:06 ` Kelvin Zhang [this message]
2026-09-03 23:11 ` [PATCH v8 02/11] f2fs: describe SIT block layout dynamically Kelvin Zhang
2026-09-03 23:11 ` [PATCH v8 03/11] f2fs: describe NAT " Kelvin Zhang
2026-09-03 23:11 ` [PATCH v8 04/11] f2fs: describe orphan " Kelvin Zhang
2026-09-03 23:11 ` [PATCH v8 05/11] f2fs: describe dentry " Kelvin Zhang
2026-09-03 23:11 ` [PATCH v8 06/11] f2fs: describe {i,d,id}node " Kelvin Zhang
2026-09-03 23:11 ` [PATCH v8 07/11] f2fs: describe xattr " Kelvin Zhang
2026-09-03 23:11 ` [PATCH v8 08/11] f2fs: parameterize sector conversion macros Kelvin Zhang
2026-09-03 23:11 ` [PATCH v8 09/11] f2fs: parameterize byte and block " Kelvin Zhang
2026-09-03 23:11 ` [PATCH v8 10/11] f2fs: describe node tree geometry dynamically Kelvin Zhang
2026-09-03 23:11 ` [PATCH v8 11/11] f2fs: parameterize block size and mask macros Kelvin Zhang
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=cd63b907d18ebef2f8dfa3c843d008c27de4ee8b.1788476500.git.zhangxp1998@gmail.com \
--to=zhangxp1998@gmail.com \
--cc=chao@kernel.org \
--cc=daeho43@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®