From: Chao Yu <chao@kernel.org>
To: Kelvin Zhang <zhangxp1998@gmail.com>,
linux-f2fs-devel@lists.sourceforge.net
Cc: chao@kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
Daeho Jeong <daeho43@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 01/11] f2fs: initialize sb_info early in f2fs_fill_super
Date: Fri, 4 Sep 2026 09:48:59 +0800 [thread overview]
Message-ID: <eae9790d-8a48-4421-94d6-1f24469e325e@kernel.org> (raw)
In-Reply-To: <41898b6a3cc76d464d6d1d8774daae6c185e88b3.1788479509.git.zhangxp1998@gmail.com>
On 9/4/26 07:54, Kelvin Zhang wrote:
> 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>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2026-09-04 1:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 23:54 [PATCH v9 00/11] f2fs: prepare metadata layouts for runtime block sizes Kelvin Zhang
2026-09-03 23:54 ` [PATCH v9 01/11] f2fs: initialize sb_info early in f2fs_fill_super Kelvin Zhang
2026-09-04 1:48 ` Chao Yu [this message]
2026-09-03 23:56 ` [PATCH v9 02/11] f2fs: describe SIT block layout dynamically Kelvin Zhang
2026-09-04 1:54 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 03/11] f2fs: describe NAT " Kelvin Zhang
2026-09-04 1:55 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 04/11] f2fs: describe orphan " Kelvin Zhang
2026-09-04 1:56 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 05/11] f2fs: describe dentry " Kelvin Zhang
2026-09-04 1:58 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 06/11] f2fs: describe {i,d,id}node " Kelvin Zhang
2026-09-04 2:08 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 07/11] f2fs: describe xattr " Kelvin Zhang
2026-09-04 2:15 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 08/11] f2fs: parameterize sector conversion macros Kelvin Zhang
2026-09-04 2:16 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 09/11] f2fs: parameterize byte and block " Kelvin Zhang
2026-09-04 2:17 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 10/11] f2fs: describe node tree geometry dynamically Kelvin Zhang
2026-09-04 2:18 ` Chao Yu
2026-09-03 23:56 ` [PATCH v9 11/11] f2fs: parameterize block size and mask macros Kelvin Zhang
2026-09-04 2:20 ` Chao Yu
2026-09-08 20:00 ` [f2fs-dev] [PATCH v9 00/11] f2fs: prepare metadata layouts for runtime block sizes patchwork-bot+f2fs
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=eae9790d-8a48-4421-94d6-1f24469e325e@kernel.org \
--to=chao@kernel.org \
--cc=daeho43@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zhangxp1998@gmail.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
all inboxes | Powered by JetHome®