From: Zhang Yi <yizhang089@gmail.com>
To: Li Chen <me@linux.beauty>, Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ext4: remove unused i_fc_wait
Date: Sat, 24 Jan 2026 16:18:47 +0800 [thread overview]
Message-ID: <f20b78a1-82c2-4864-a996-585c703573e7@gmail.com> (raw)
In-Reply-To: <20260120121941.144192-1-me@linux.beauty>
On 1/20/2026 8:19 PM, Li Chen wrote:
> i_fc_wait is only initialized in ext4_fc_init_inode() and never used for
> waiting or wakeups. Drop it.
>
> Signed-off-by: Li Chen <me@linux.beauty>
Thank you for the cleanup, it looks good to me.
Reviewed-by: Zhang Yi <yi.zhang@huawei.com>
> ---
> fs/ext4/ext4.h | 4 ----
> fs/ext4/fast_commit.c | 2 +-
> 2 files changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
> index 56112f201cac..dc3a5a926eff 100644
> --- a/fs/ext4/ext4.h
> +++ b/fs/ext4/ext4.h
> @@ -28,7 +28,6 @@
> #include <linux/seqlock.h>
> #include <linux/mutex.h>
> #include <linux/timer.h>
> -#include <linux/wait.h>
> #include <linux/sched/signal.h>
> #include <linux/blockgroup_lock.h>
> #include <linux/percpu_counter.h>
> @@ -1091,9 +1090,6 @@ struct ext4_inode_info {
>
> spinlock_t i_raw_lock; /* protects updates to the raw inode */
>
> - /* Fast commit wait queue for this inode */
> - wait_queue_head_t i_fc_wait;
> -
> /*
> * Protect concurrent accesses on i_fc_lblk_start, i_fc_lblk_len
> * and inode's EXT4_FC_STATE_COMMITTING state bit.
> diff --git a/fs/ext4/fast_commit.c b/fs/ext4/fast_commit.c
> index fa66b08de999..86789989b3f4 100644
> --- a/fs/ext4/fast_commit.c
> +++ b/fs/ext4/fast_commit.c
> @@ -13,6 +13,7 @@
> #include "mballoc.h"
>
> #include <linux/lockdep.h>
> +#include <linux/wait_bit.h>
> /*
> * Ext4 Fast Commits
> * -----------------
> @@ -215,7 +216,6 @@ void ext4_fc_init_inode(struct inode *inode)
> ext4_clear_inode_state(inode, EXT4_STATE_FC_COMMITTING);
> INIT_LIST_HEAD(&ei->i_fc_list);
> INIT_LIST_HEAD(&ei->i_fc_dilist);
> - init_waitqueue_head(&ei->i_fc_wait);
> }
>
> static bool ext4_fc_disabled(struct super_block *sb)
next prev parent reply other threads:[~2026-01-24 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 12:19 Li Chen
2026-01-24 8:18 ` Zhang Yi [this message]
2026-04-10 15:18 ` Theodore Ts'o
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=f20b78a1-82c2-4864-a996-585c703573e7@gmail.com \
--to=yizhang089@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@linux.beauty \
--cc=tytso@mit.edu \
/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®