From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Ruipeng Qi <ruipengqi3@gmail.com>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: fix potential deadlock in f2fs_balance_fs()
Date: Mon, 11 May 2026 01:41:13 +0000 [thread overview]
Message-ID: <177846367379.1975880.11629604282967011707.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260502124157.3406780-1-ruipengqi3@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sat, 2 May 2026 20:41:57 +0800 you wrote:
> From: Ruipeng Qi <ruipengqi3@gmail.com>
>
> When the f2fs filesystem space is nearly exhausted, we encounter deadlock
> issues as below:
>
> INFO: task A:1890 blocked for more than 120 seconds.
> Tainted: G O 6.12.41-g3fe07ddf05ab #1
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> task:A state:D stack:0 pid:1890 tgid:1626 ppid:1153 flags:0x00000204
> Call trace:
> __switch_to+0xf4/0x158
> __schedule+0x27c/0x908
> schedule+0x3c/0x118
> io_schedule+0x44/0x68
> folio_wait_bit_common+0x174/0x370
> folio_wait_bit+0x20/0x38
> folio_wait_writeback+0x54/0xc8
> truncate_inode_partial_folio+0x70/0x1e0
> truncate_inode_pages_range+0x1b0/0x450
> truncate_pagecache+0x54/0x88
> f2fs_file_write_iter+0x3e8/0xb80
> do_iter_readv_writev+0xf0/0x1e0
> vfs_writev+0x138/0x2c8
> do_writev+0x88/0x130
> __arm64_sys_writev+0x28/0x40
> invoke_syscall+0x50/0x120
> el0_svc_common.constprop.0+0xc8/0xf0
> do_el0_svc+0x24/0x38
> el0_svc+0x30/0xf8
> el0t_64_sync_handler+0x120/0x130
> el0t_64_sync+0x190/0x198
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3] f2fs: fix potential deadlock in f2fs_balance_fs()
https://git.kernel.org/jaegeuk/f2fs/c/65ab67d250f6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2026-05-11 1:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-02 12:41 [f2fs-dev] [PATCH v3] f2fs: fix potential deadlock in f2fs_balance_fs() ruipengqi
2026-05-03 9:47 ` Chao Yu via Linux-f2fs-devel
2026-05-10 12:10 ` Ruipeng Qi
2026-05-11 1:41 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
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=177846367379.1975880.11629604282967011707.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=ruipengqi3@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