mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, chaseyu@google.com, ruipengqi3@gmail.com,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net, stable@kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix potential deadlock in gc_merge path of f2fs_balance_fs()
Date: Fri, 22 May 2026 04:30:09 +0000	[thread overview]
Message-ID: <177942420913.624124.6855697995437487075.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260519011438.1168155-1-chao@kernel.org>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Tue, 19 May 2026 01:14:38 +0000 you wrote:
> When we mount device w/ gc_merge mount option, we may suffer below
> potential deadlock:
> 
> Kworker					GC trehad			Truncator
> - f2fs_write_cache_pages
>  - f2fs_write_single_data_page
>   - f2fs_do_write_data_page
>    - folio_start_writeback  --- set writeback flag on folio
>    - f2fs_outplace_write_data
>    : cached folio in internal bio cache
>   - f2fs_balance_fs
>    - wake_up(gc_thread)
>    : wake up gc thread to run foreground GC
>    - finish_wait(fggc_wq)
>    : wait on the waitqueue --- wait on GC thread to finish the work
> 									- truncate_inode_pages_range
> 									 - __filemap_get_folio(, FGP_LOCK)  --- lock folio
> 									 - truncate_inode_partial_folio
> 									  - folio_wait_writeback            --- wait on writeback being cleared
> 					- do_garbage_collect
> 					 - move_data_page
> 					  - f2fs_get_lock_data_folio
> 					   - lock on folio  --- blocked on folio's lock
> 
> [...]

Here is the summary with links:
  - [f2fs-dev] f2fs: fix potential deadlock in gc_merge path of f2fs_balance_fs()
    https://git.kernel.org/jaegeuk/f2fs/c/cf69827e772c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-05-22  4:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19  1:14 Chao Yu
2026-05-22  4:30 ` patchwork-bot+f2fs [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=177942420913.624124.6855697995437487075.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=chao@kernel.org \
    --cc=chaseyu@google.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ruipengqi3@gmail.com \
    --cc=stable@kernel.org \
    /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