From: Julian Sun <sunjunchao@bytedance.com>
To: Huacai Chen <chenhuacai@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, Xuefeng Li <lixuefeng@loongson.cn>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] writeback: Fix wakeup and logging timeouts for !DETECT_HUNG_TASK
Date: Mon, 2 Feb 2026 10:27:50 +0800 [thread overview]
Message-ID: <2538bda2-e14a-4ae0-a32d-e944ca44b37f@bytedance.com> (raw)
In-Reply-To: <20260131090724.4128443-1-chenhuacai@loongson.cn>
On 1/31/26 5:07 PM, Huacai Chen wrote:
> Recent changes of fs-writeback cause such warnings if DETECT_HUNG_TASK
> is not enabled:
>
> INFO: The task sync:1342 has been waiting for writeback completion for more than 1 seconds.
>
> The reason is sysctl_hung_task_timeout_secs is 0 when DETECT_HUNG_TASK
> is not enabled, then it causes the warning message even if the writeback
> lasts for only one second.
>
> I believe the wakeup and logging is also useful for !DETECT_HUNG_TASK,
> so I don't want to disable them completely. As DEFAULT_HUNG_TASK_TIMEOUT
> is 120 seconds, so for the !DETECT_HUNG_TASK case let's use 120 seconds
> instead of sysctl_hung_task_timeout_secs.
>
> Fixes: 1888635532fb ("writeback: Wake up waiting tasks when finishing the writeback of a chunk.")
> Fixes: d6e621590764 ("writeback: Add logging for slow writeback (exceeds sysctl_hung_task_timeout_secs)")
> Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
> ---
> fs/fs-writeback.c | 15 ++++++++++++---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
> index 5444fc706ac7..847e46f0e019 100644
> --- a/fs/fs-writeback.c
> +++ b/fs/fs-writeback.c
> @@ -198,10 +198,15 @@ static void wb_queue_work(struct bdi_writeback *wb,
>
> static bool wb_wait_for_completion_cb(struct wb_completion *done)
> {
> +#ifndef CONFIG_DETECT_HUNG_TASK
> + unsigned long hung_secs = 120;
> +#else
> + unsigned long hung_secs = sysctl_hung_task_timeout_secs;
> +#endif
> unsigned long waited_secs = (jiffies - done->wait_start) / HZ;
>
> done->progress_stamp = jiffies;
> - if (waited_secs > sysctl_hung_task_timeout_secs)
> + if (waited_secs > hung_secs)
> pr_info("INFO: The task %s:%d has been waiting for writeback "
> "completion for more than %lu seconds.",
> current->comm, current->pid, waited_secs);
> @@ -1947,6 +1952,11 @@ static long writeback_sb_inodes(struct super_block *sb,
> long write_chunk;
> long total_wrote = 0; /* count both pages and inodes */
> unsigned long dirtied_before = jiffies;
> +#ifndef CONFIG_DETECT_HUNG_TASK
> + unsigned long hung_secs = 120;
> +#else
> + unsigned long hung_secs = sysctl_hung_task_timeout_secs;
> +#endif
>
> if (work->for_kupdate)
> dirtied_before = jiffies -
> @@ -2031,8 +2041,7 @@ static long writeback_sb_inodes(struct super_block *sb,
>
> /* Report progress to inform the hung task detector of the progress. */
> if (work->done && work->done->progress_stamp &&
> - (jiffies - work->done->progress_stamp) > HZ *
> - sysctl_hung_task_timeout_secs / 2)
> + (jiffies - work->done->progress_stamp) > HZ * hung_secs / 2)
> wake_up_all(work->done->waitq);
>
> wbc_detach_inode(&wbc);
Thanks for the patch, looks good to me.
Reviewed-by: Julian Sun <sunjunchao@bytedance.com>
--
Julian Sun <sunjunchao@bytedance.com>
next prev parent reply other threads:[~2026-02-02 2:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 9:07 Huacai Chen
2026-02-02 2:27 ` Julian Sun [this message]
2026-02-02 12:49 ` Jan Kara
2026-02-03 2:46 ` Huacai Chen
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=2538bda2-e14a-4ae0-a32d-e944ca44b37f@bytedance.com \
--to=sunjunchao@bytedance.com \
--cc=brauner@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--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