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, stable@kernel.org,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to avoid potential deadloop in f2fs_fsync_node_pages()
Date: Tue, 25 Aug 2026 15:40:06 +0000	[thread overview]
Message-ID: <178767240663.3943858.7250949044919337170.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260824131729.3694378-1-chao@kernel.org>

Hello:

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

On Mon, 24 Aug 2026 21:17:29 +0800 you wrote:
> There is potential deadloop in race condition:
> 
> Thread A				Thread B
> - fsync
>  - f2fs_do_sync_file
>   - f2fs_fsync_node_pages
>    - last_fsync_dnode
>     - folio_get(last_folio)
> 					- f2fs_setattr
> 					 - f2fs_truncate
> 					  - f2fs_truncate_blocks
> 					   - f2fs_do_truncate_blocks
> 					    - f2fs_truncate_inode_blocks
> 					     - truncate_dnode
> 					      - truncate_node
> 					       - invalidate_mapping_pages
> 					        - folio->mapping = NULL
>    - is_node_folio alwasy return false
>    - atomic && !marked is always true,
>      then goto retry
> 
> [...]

Here is the summary with links:
  - [f2fs-dev] f2fs: fix to avoid potential deadloop in f2fs_fsync_node_pages()
    https://git.kernel.org/jaegeuk/f2fs/c/ce366bfa821e

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



  reply	other threads:[~2026-08-25 15:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 13:17 Chao Yu
2026-08-25 15:40 ` patchwork-bot+f2fs [this message]
2026-09-09  1:12 ` [f2fs-dev] " Zhiguo Niu
2026-09-09  2:03   ` Chao Yu
2026-09-09  2:12     ` Zhiguo Niu

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=178767240663.3943858.7250949044919337170.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --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
all inboxes | Powered by JetHome®