Re: [f2fs-dev] [PATCH] f2fs: fix to avoid invalid wait context issue

[patchwork-bot+f2fs@kernel.org]

Hello:

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

On Wed, 11 Jun 2025 16:42:18 +0800 you wrote:
> =============================
> [ BUG: Invalid wait context ]
> 6.13.0-rc1 #84 Tainted: G           O
> -----------------------------
> cat/56160 is trying to lock:
> ffff888105c86648 (&cprc->stat_lock){+.+.}-{3:3}, at: update_general_status+0x32a/0x8c0 [f2fs]
> other info that might help us debug this:
> context-{5:5}
> 2 locks held by cat/56160:
>  #0: ffff88810a002a98 (&p->lock){+.+.}-{4:4}, at: seq_read_iter+0x56/0x4c0
>  #1: ffffffffa0462638 (f2fs_stat_lock){....}-{2:2}, at: stat_show+0x29/0x1020 [f2fs]
> stack backtrace:
> CPU: 0 UID: 0 PID: 56160 Comm: cat Tainted: G           O       6.13.0-rc1 #84
> Tainted: [O]=OOT_MODULE
> Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
> Call Trace:
>  <TASK>
>  dump_stack_lvl+0x88/0xd0
>  dump_stack+0x14/0x20
>  __lock_acquire+0x8d4/0xbb0
>  lock_acquire+0xd6/0x300
>  _raw_spin_lock+0x38/0x50
>  update_general_status+0x32a/0x8c0 [f2fs]
>  stat_show+0x50/0x1020 [f2fs]
>  seq_read_iter+0x116/0x4c0
>  seq_read+0xfa/0x130
>  full_proxy_read+0x66/0x90
>  vfs_read+0xc4/0x350
>  ksys_read+0x74/0xf0
>  __x64_sys_read+0x1d/0x20
>  x64_sys_call+0x17d9/0x1b80
>  do_syscall_64+0x68/0x130
>  entry_SYSCALL_64_after_hwframe+0x67/0x6f
> RIP: 0033:0x7f2ca53147e2
> 
> [...]

Here is the summary with links:
  - [f2fs-dev] f2fs: fix to avoid invalid wait context issue
    https://git.kernel.org/jaegeuk/f2fs/c/90d5c9ba3ed9

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