Re: [f2fs-dev] [PATCH] f2fs: use f2fs_{down, up}_(read, write}_trace() for nat_tree_lock

patchwork-bot+f2fs--- via Linux-f2fs-devel <[email protected]>
Newsgroups net.sourceforge.lists.linux-f2fs-devel,org.kernel.vger.linux-kernel
Message-ID <178732740714.1339488.2738118422362472739.git-patchwork-notify@kernel.org>
Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <[email protected]>:

On Mon, 17 Aug 2026 11:19:16 +0000 you wrote:
> Under heavy workloads or during background GC/fallocate operations,
> nat_tree_lock can experience high lock contention between background
> readers (e.g. f2fs_get_node_info() in gc_data_segment) and writers
> (e.g. flush_nat_entries, set_node_addr, shrinker).
> 
> [375067.327986][T13777]  schedule+0x4c/0x114
> [375067.327997][T13777]  f2fs_get_node_info+0x438/0x5c4
> [375067.328002][T13777]  f2fs_get_inode_page+0x1e0/0x3f0
> [375067.328013][T13777]  f2fs_iget+0x88/0x1180
> [375067.328024][T13777]  f2fs_lookup+0x168/0x3a8
> [375067.328035][T13777]  path_openat+0xa28/0x1b04
> [375067.328046][T13777]  do_filp_open+0xac/0x130
> [375067.328056][T13777]  do_sys_openat2+0x140/0x21c
> [375067.328066][T13777]  __arm64_sys_openat+0x70/0x9c
> 
> [...]

Here is the summary with links:
  - [f2fs-dev] f2fs: use f2fs_{down, up}_(read, write}_trace() for nat_tree_lock
    https://git.kernel.org/jaegeuk/f2fs/c/f9c899ec50ab

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
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.