From: Zhang Yi <yi.zhang@huaweicloud.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
bcrl@kvack.org, tytso@mit.edu, adilger.kernel@dilger.ca,
libaokun@linux.alibaba.com, ojaswin@linux.ibm.com,
ritesh.list@gmail.com, pmladek@suse.com, rostedt@goodmis.org,
andriy.shevchenko@linux.intel.com, linux@rasmusvillemoes.dk,
senozhatsky@chromium.org, akpm@linux-foundation.org,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, socketcan@hartkopp.net,
mkl@pengutronix.de, kuniyu@google.com, willemb@google.com,
jhs@mojatatu.com, jiri@resnulli.us, kees@kernel.org,
cyphar@cyphar.com, tglx@kernel.org, liuhangbin@gmail.com,
sdf@fomichev.me, nb@tipi-net.de, linux-fsdevel@vger.kernel.org,
linux-aio@kvack.org, linux-kernel@vger.kernel.org,
linux-ext4@vger.kernel.org, netdev@vger.kernel.org,
linux-can@vger.kernel.org
Subject: Re: [PATCH 07/11] ext4: Convert group-count barrier protocol to acquire/release
Date: Mon, 31 Aug 2026 20:18:39 +0800 [thread overview]
Message-ID: <49d6df68-dd74-417d-a313-69d15846c2b7@huaweicloud.com> (raw)
In-Reply-To: <20260825095422.3166067-8-ruanjinjie@huawei.com>
On 8/25/2026 5:54 PM, Jinjie Ruan wrote:
> During an online resize, reading s_groups_count and s_blockfile_groups
> requires strict ordering against subsequent initialized block group
> metadata.
>
> Replace the historical smp_wmb()/smp_rmb() pairs with smp_store_release()
> and smp_load_acquire(). This formalizes the publish-subscribe pattern
> and allows weakly-ordered architectures (e.g., arm64) to utilize native
> STLR/LDAR instructions instead of full DMB fences.
>
> Update the documentation in resize.c and ext4.h accordingly.
>
> Assisted-by: Gemini:Gemini-3.1
> Assisted-by: DeepSeek:DeepSeek-V3
> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
Looks good to me.
Reviewed-by: Zhang Yi <yi.zhang@huawei.com>
> ---
> fs/ext4/ext4.h | 10 +++-------
> fs/ext4/mballoc.c | 6 ++----
> fs/ext4/resize.c | 19 +++++++++++--------
> 3 files changed, 16 insertions(+), 19 deletions(-)
>
> diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
> index 724a27e8be61..d70b9cb09155 100644
> --- a/fs/ext4/ext4.h
> +++ b/fs/ext4/ext4.h
> @@ -3542,16 +3542,12 @@ static inline void ext4_isize_set(struct ext4_inode *raw_inode, loff_t i_size)
> }
>
> /*
> - * Reading s_groups_count requires using smp_rmb() afterwards. See
> - * the locking protocol documented in the comments of ext4_group_add()
> - * in resize.c
> + * Reading s_groups_count uses acquire semantics.
> */
> static inline ext4_group_t ext4_get_groups_count(struct super_block *sb)
> {
> - ext4_group_t ngroups = EXT4_SB(sb)->s_groups_count;
> -
> - smp_rmb();
> - return ngroups;
> + /* Pairs with smp_store_release() in ext4_update_super() */
> + return smp_load_acquire(&EXT4_SB(sb)->s_groups_count);
> }
>
> static inline ext4_group_t ext4_flex_group(struct ext4_sb_info *sbi,
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index 06171a11db12..a15285224cdf 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -899,10 +899,8 @@ static ext4_group_t ext4_get_allocation_groups_count(
>
> /* non-extent files are limited to low blocks/groups */
> if (!(ext4_test_inode_flag(ac->ac_inode, EXT4_INODE_EXTENTS)))
> - ngroups = EXT4_SB(ac->ac_sb)->s_blockfile_groups;
> -
> - /* Pairs with smp_wmb() in ext4_update_super() */
> - smp_rmb();
> + /* Pairs with smp_store_release() in ext4_update_super() */
> + ngroups = smp_load_acquire(&EXT4_SB(ac->ac_sb)->s_blockfile_groups);
>
> return ngroups;
> }
> diff --git a/fs/ext4/resize.c b/fs/ext4/resize.c
> index 2c5b851c552a..5e3ad8393cf8 100644
> --- a/fs/ext4/resize.c
> +++ b/fs/ext4/resize.c
> @@ -1462,11 +1462,11 @@ static void ext4_update_super(struct super_block *sb,
> *
> * The precise rules we use are:
> *
> - * * Writers must perform a smp_wmb() after updating all
> - * dependent data and before modifying the groups count
> + * * Writers must use a release store when updating the groups count
> + * after all dependent data has been updated
> *
> - * * Readers must perform an smp_rmb() after reading the groups
> - * count and before reading any dependent data.
> + * * Readers must use an acquire load when reading the groups
> + * count before reading any dependent data.
> *
> * NB. These rules can be relaxed when checking the group count
> * while freeing data, as we can only allocate from a block
> @@ -1474,12 +1474,15 @@ static void ext4_update_super(struct super_block *sb,
> * only then free after serialising in turn against that
> * allocation.
> */
> - smp_wmb();
>
> /* Update the global fs size fields */
> - sbi->s_groups_count += flex_gd->count;
> - sbi->s_blockfile_groups = min(sbi->s_groups_count,
> - (EXT4_MAX_BLOCK_FILE_PHYS / EXT4_BLOCKS_PER_GROUP(sb)));
> + /* Pairs with smp_load_acquire() in ext4_get_groups_count() */
> + smp_store_release(&sbi->s_groups_count,
> + sbi->s_groups_count + flex_gd->count);
> + /* Pairs with smp_load_acquire() in ext4_get_allocation_groups_count() */
> + smp_store_release(&sbi->s_blockfile_groups,
> + min(sbi->s_groups_count,
> + (EXT4_MAX_BLOCK_FILE_PHYS / EXT4_BLOCKS_PER_GROUP(sb))));
>
> /* Update the reserved block counts only once the new group is
> * active. */
next prev parent reply other threads:[~2026-08-31 12:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 9:54 [PATCH 00/11] Convert barrier pairs to acquire/release for better performance Jinjie Ruan
2026-08-25 9:54 ` [PATCH 01/11] user_namespace: Use acquire/release for nr_extents synchronization Jinjie Ruan
2026-08-26 9:54 ` sashiko-bot
2026-09-01 1:42 ` Jinjie Ruan
2026-08-25 9:54 ` [PATCH 02/11] lib/vsprintf: Use acquire/release for ptr_key publication Jinjie Ruan
2026-08-26 9:54 ` sashiko-bot
2026-08-25 9:54 ` [PATCH 03/11] fs: aio: Use acquire/release for ring->tail publication Jinjie Ruan
2026-08-26 9:54 ` sashiko-bot
2026-08-31 12:13 ` Jan Kara
2026-09-01 1:44 ` Jinjie Ruan
2026-08-25 9:54 ` [PATCH 04/11] fs: Use acquire/release for fdtable resize synchronization Jinjie Ruan
2026-08-26 9:54 ` sashiko-bot
2026-08-31 12:22 ` Jan Kara
2026-08-25 9:54 ` [PATCH 05/11] pidfs: Use test_bit_acquire() for attr flag tests Jinjie Ruan
2026-08-26 9:54 ` sashiko-bot
2026-08-25 9:54 ` [PATCH 06/11] super: Use acquire for SB_BORN check in super_cache_count() Jinjie Ruan
2026-08-26 9:54 ` sashiko-bot
2026-08-31 12:29 ` Jan Kara
2026-08-31 12:46 ` Jinjie Ruan
2026-08-25 9:54 ` [PATCH 07/11] ext4: Convert group-count barrier protocol to acquire/release Jinjie Ruan
2026-08-26 9:54 ` sashiko-bot
2026-08-31 11:53 ` Jan Kara
2026-08-31 12:18 ` Zhang Yi [this message]
2026-08-25 9:54 ` [PATCH 08/11] soreuseport: publish num_socks with acquire/release Jinjie Ruan
2026-08-26 9:54 ` sashiko-bot
2026-08-25 9:54 ` [PATCH 09/11] net: sched: act_gact: use acquire/release for tcfg_ptype Jinjie Ruan
2026-08-26 9:54 ` sashiko-bot
2026-08-25 9:54 ` [PATCH 10/11] 8021q: publish vlan_devices_arrays entries with acquire/release Jinjie Ruan
2026-08-26 9:54 ` sashiko-bot
2026-08-25 9:54 ` [PATCH 11/11] can: isotp: publish tx.state with smp_store_release() Jinjie Ruan
2026-08-25 11:46 ` Oliver Hartkopp
2026-08-26 3:33 ` Jinjie Ruan
2026-08-26 8:04 ` Oliver Hartkopp
2026-08-26 9:54 ` sashiko-bot
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=49d6df68-dd74-417d-a313-69d15846c2b7@huaweicloud.com \
--to=yi.zhang@huaweicloud.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bcrl@kvack.org \
--cc=brauner@kernel.org \
--cc=cyphar@cyphar.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jack@suse.cz \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=libaokun@linux.alibaba.com \
--cc=linux-aio@kvack.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=liuhangbin@gmail.com \
--cc=mkl@pengutronix.de \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=pabeni@redhat.com \
--cc=pmladek@suse.com \
--cc=ritesh.list@gmail.com \
--cc=rostedt@goodmis.org \
--cc=ruanjinjie@huawei.com \
--cc=sdf@fomichev.me \
--cc=senozhatsky@chromium.org \
--cc=socketcan@hartkopp.net \
--cc=tglx@kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willemb@google.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