syzbot
WARNING: still has locks held in io_ring_submit_lock
Status:
fixed on 2023/02/24 13:50
Subsystems:
fs
io-uring
[Documentation on labels]
Reported-by: syzbot+987d7bb19195ae45208c@syzkaller.appspotmail.com
Fix commit:
e7637a492b9f
io_uring: fix locking state for empty buffer group
First crash: 1532d, last: 1531d
▶
▼
Last patch testing requests (2)
Sample crash report:
====================================
WARNING: iou-wrk-3613/3623 still has locks held!
5.18.0-rc6-next-20220513-syzkaller #0 Not tainted
------------------------------------
1 lock held by iou-wrk-3613/3623:
#0: ffff888140bfe0a8 (&ctx->uring_lock){+.+.}-{3:3}, at: io_ring_submit_lock+0x75/0xc0 fs/io_uring.c:1494
stack backtrace:
CPU: 0 PID: 3623 Comm: iou-wrk-3613 Not tainted 5.18.0-rc6-next-20220513-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
try_to_freeze include/linux/freezer.h:66 [inline]
get_signal+0x1424/0x2600 kernel/signal.c:2647
io_wqe_worker+0x64b/0xdb0 fs/io-wq.c:663
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:297
</TASK>
* Struck through repros no longer work on HEAD.