From: Baokun Li <libaokun@linux.alibaba.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
brauner@kernel.org, tj@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] writeback: drop now-unnecessary rcu_barrier() in cgroup_writeback_umount()
Date: Mon, 18 May 2026 21:10:20 +0800 [thread overview]
Message-ID: <306ba367-0e84-465f-8449-d88c45eb68b7@linux.alibaba.com> (raw)
In-Reply-To: <q75moaoyuys22umiai3h6jnrowes37rrif2ap6v44j7vgd7qgw@lx4esnq6stjg>
在 2026/5/18 21:01, Jan Kara 写道:
> On Sun 17-05-26 22:21:31, Baokun Li wrote:
>> Commit e1b849cfa6b6 ("writeback: Avoid contention on wb->list_lock when
>> switching inodes") replaced the queue_rcu_work() based scheduling of
>> inode wb switches with a plain queue_work(). Since then no switcher
>> goes through call_rcu(), so rcu_barrier() in cgroup_writeback_umount()
>> has no work to wait for and is effectively a no-op.
>>
>> Fixes: e1b849cfa6b6 ("writeback: Avoid contention on wb->list_lock when switching inodes")
>> Signed-off-by: Baokun Li <libaokun@linux.alibaba.com>
> Looks good. Just I think this should be folded in patch 1, since you have
> proper Fixes tag, I don't think there's a concern this would be backported
> to kernels where rcu_barrier() is still needed.
>
> Honza
Thank you for your review!
Because the two patches have different fix tags, there is concern that
removing rcu_barrier here could cause the stable branches still using
queue_rcu_work (5.10.y, 6.6.y, ...) to reintroduce similar issues when
the round of fix patches deletes this necessary synchronization.
Therefore, the patches are split into two to make their purposes clearer.
Cheers,
Baokun
>> ---
>> fs/fs-writeback.c | 5 -----
>> 1 file changed, 5 deletions(-)
>>
>> diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
>> index 1f95ddcee363..9ae290547eb2 100644
>> --- a/fs/fs-writeback.c
>> +++ b/fs/fs-writeback.c
>> @@ -1246,11 +1246,6 @@ void cgroup_writeback_umount(struct super_block *sb)
>> * will then drain it.
>> */
>> synchronize_rcu();
>> - /*
>> - * Use rcu_barrier() to wait for all pending callbacks to
>> - * ensure that all in-flight wb switches are in the workqueue.
>> - */
>> - rcu_barrier();
>> flush_workqueue(isw_wq);
>> }
>> }
>> --
>> 2.43.7
>>
next prev parent reply other threads:[~2026-05-18 13:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 14:21 [PATCH v2 0/3] writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() Baokun Li
2026-05-17 14:21 ` [PATCH v2 1/3] " Baokun Li
2026-05-18 12:58 ` Jan Kara
2026-05-17 14:21 ` [PATCH v2 2/3] writeback: drop now-unnecessary rcu_barrier() in cgroup_writeback_umount() Baokun Li
2026-05-18 13:01 ` Jan Kara
2026-05-18 13:10 ` Baokun Li [this message]
2026-05-18 15:11 ` Jan Kara
2026-05-17 14:21 ` [PATCH v2 3/3] writeback: use a per-sb counter to drain inode wb switches at umount Baokun Li
2026-05-18 11:14 ` Baokun Li
2026-05-18 11:42 ` Christian Brauner
2026-05-18 11:52 ` Baokun Li
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=306ba367-0e84-465f-8449-d88c45eb68b7@linux.alibaba.com \
--to=libaokun@linux.alibaba.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
Powered by JetHome