From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to avoid invalid wait context issue
Date: Tue, 24 Jun 2025 00:41:00 +0000 [thread overview]
Message-ID: <175072566023.3346761.5670110283778494132.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250611084218.62774-1-chao@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
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to avoid invalid wait context issue
Date: Tue, 24 Jun 2025 00:41:00 +0000 [thread overview]
Message-ID: <175072566023.3346761.5670110283778494132.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250611084218.62774-1-chao@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
next prev parent reply other threads:[~2025-06-24 0:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 8:42 [f2fs-dev] [PATCH] f2fs: fix to avoid invalid wait context issue Chao Yu via Linux-f2fs-devel
2025-06-11 8:42 ` Chao Yu
2025-06-24 0:41 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-06-24 0:41 ` [f2fs-dev] " patchwork-bot+f2fs
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=175072566023.3346761.5670110283778494132.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.