======================================================
WARNING: possible circular locking dependency detected
6.1.135-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor/4614 is trying to acquire lock:
ffff8880683a8138 ((wq_completion)ocfs2_wq){+.+.}-{0:0}, at: __flush_workqueue+0x124/0x1380 kernel/workqueue.c:2812
but task is already holding lock:
ffff8880476420e0 (&type->s_umount_key#110){++++}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:362
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 (&type->s_umount_key#110){++++}-{3:3}:
down_read+0x42/0x2d0 kernel/locking/rwsem.c:1520
ocfs2_finish_quota_recovery+0x129/0x1e40 fs/ocfs2/quota_local.c:600
ocfs2_complete_recovery+0x157c/0x23a0 fs/ocfs2/journal.c:1324
process_one_work+0x898/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1250 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
-> #1 ((work_completion)(&journal->j_recovery_work)){+.+.}-{0:0}:
process_one_work+0x7d9/0x1160 kernel/workqueue.c:2268
worker_thread+0xaa2/0x1250 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
-> #0 ((wq_completion)ocfs2_wq){+.+.}-{0:0}:
check_prev_add kernel/locking/lockdep.c:3090 [inline]
check_prevs_add kernel/locking/lockdep.c:3209 [inline]
validate_chain kernel/locking/lockdep.c:3825 [inline]
__lock_acquire+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049
lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662
__flush_workqueue+0x13d/0x1380 kernel/workqueue.c:2812
ocfs2_shutdown_local_alloc+0xe4/0xa10 fs/ocfs2/localalloc.c:379
ocfs2_dismount_volume+0x1f4/0x920 fs/ocfs2/super.c:1879
generic_shutdown_super+0x130/0x340 fs/super.c:501
kill_block_super+0x7c/0xe0 fs/super.c:1470
deactivate_locked_super+0x93/0xf0 fs/super.c:332
cleanup_mnt+0x463/0x4f0 fs/namespace.c:1186
task_work_run+0x1ca/0x250 kernel/task_work.c:203
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:303
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
other info that might help us debug this:
Chain exists of:
(wq_completion)ocfs2_wq --> (work_completion)(&journal->j_recovery_work) --> &type->s_umount_key#110
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&type->s_umount_key#110);
lock((work_completion)(&journal->j_recovery_work));
lock(&type->s_umount_key#110);
lock((wq_completion)ocfs2_wq);
*** DEADLOCK ***
1 lock held by syz-executor/4614:
#0: ffff8880476420e0 (&type->s_umount_key#110){++++}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:362
stack backtrace:
CPU: 1 PID: 4614 Comm: syz-executor Not tainted 6.1.135-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106
check_noncircular+0x274/0x310 kernel/locking/lockdep.c:2170
check_prev_add kernel/locking/lockdep.c:3090 [inline]
check_prevs_add kernel/locking/lockdep.c:3209 [inline]
validate_chain kernel/locking/lockdep.c:3825 [inline]
__lock_acquire+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049
lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662
__flush_workqueue+0x13d/0x1380 kernel/workqueue.c:2812
ocfs2_shutdown_local_alloc+0xe4/0xa10 fs/ocfs2/localalloc.c:379
ocfs2_dismount_volume+0x1f4/0x920 fs/ocfs2/super.c:1879
generic_shutdown_super+0x130/0x340 fs/super.c:501
kill_block_super+0x7c/0xe0 fs/super.c:1470
deactivate_locked_super+0x93/0xf0 fs/super.c:332
cleanup_mnt+0x463/0x4f0 fs/namespace.c:1186
task_work_run+0x1ca/0x250 kernel/task_work.c:203
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:303
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f1ea478fc97
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffe7a1a5a48 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f1ea481089d RCX: 00007f1ea478fc97
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffe7a1a5b00
RBP: 00007ffe7a1a5b00 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffe7a1a6b90
R13: 00007f1ea481089d R14: 00000000000ca32a R15: 00007ffe7a1a6bd0
</TASK>
ocfs2: Unmounting device (7,3) on (node local)