============================================ WARNING: possible recursive locking detected 5.16.0-rc5-syzkaller #0 Not tainted -------------------------------------------- iou-wrk-8569/8581 is trying to acquire lock: ffff888023d47018 (&wqe->lock){+.+.}-{2:2}, at: io_worker_cancel_cb+0xf1/0x210 fs/io-wq.c:187 but task is already holding lock: ffff888023d47018 (&wqe->lock){+.+.}-{2:2}, at: io_wq_worker_sleeping+0xc2/0x120 fs/io-wq.c:700 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&wqe->lock); lock(&wqe->lock); *** DEADLOCK *** May be due to missing lock nesting notation 1 lock held by iou-wrk-8569/8581: #0: ffff888023d47018 (&wqe->lock){+.+.}-{2:2}, at: io_wq_worker_sleeping+0xc2/0x120 fs/io-wq.c:700 stack backtrace: CPU: 1 PID: 8581 Comm: iou-wrk-8569 Not tainted 5.16.0-rc5-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_deadlock_bug kernel/locking/lockdep.c:2956 [inline] check_deadlock kernel/locking/lockdep.c:2999 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire.cold+0x149/0x3ab kernel/locking/lockdep.c:5027 lock_acquire kernel/locking/lockdep.c:5637 [inline] lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5602 __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline] _raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154 io_worker_cancel_cb+0xf1/0x210 fs/io-wq.c:187 io_wq_cancel_tw_create fs/io-wq.c:1220 [inline] io_queue_worker_create+0x5a7/0x630 fs/io-wq.c:372 io_wqe_dec_running+0x1ce/0x210 fs/io-wq.c:398 io_wq_worker_sleeping+0xca/0x120 fs/io-wq.c:701 sched_submit_work kernel/sched/core.c:6295 [inline] schedule+0x1d0/0x260 kernel/sched/core.c:6323 schedule_timeout+0x14a/0x2a0 kernel/time/timer.c:1881 io_wqe_worker+0x4bd/0xcb0 fs/io-wq.c:645 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295