====================================================== WARNING: possible circular locking dependency detected 6.14.0-rc7-syzkaller-00205-g586de92313fc #0 Not tainted ------------------------------------------------------ syz-executor/18759 is trying to acquire lock: ffff888033c48148 ((wq_completion)ocfs2_wq){+.+.}-{0:0}, at: touch_wq_lockdep_map+0xa7/0x1c0 kernel/workqueue.c:3907 but task is already holding lock: ffff8880564fc0e0 (&type->s_umount_key#105){++++}-{4:4}, at: __super_lock fs/super.c:56 [inline] ffff8880564fc0e0 (&type->s_umount_key#105){++++}-{4:4}, at: __super_lock_excl fs/super.c:71 [inline] ffff8880564fc0e0 (&type->s_umount_key#105){++++}-{4:4}, at: deactivate_super+0xd6/0x100 fs/super.c:505 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&type->s_umount_key#105){++++}-{4:4}: down_read+0x9a/0x330 kernel/locking/rwsem.c:1524 ocfs2_finish_quota_recovery+0xeb/0xcd0 fs/ocfs2/quota_local.c:603 ocfs2_complete_recovery+0x302/0xf90 fs/ocfs2/journal.c:1357 process_one_work+0x9c8/0x1ba0 kernel/workqueue.c:3238 process_scheduled_works kernel/workqueue.c:3319 [inline] worker_thread+0x6c8/0xf00 kernel/workqueue.c:3400 kthread+0x3b2/0x750 kernel/kthread.c:464 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 -> #1 ((work_completion)(&journal->j_recovery_work)){+.+.}-{0:0}: process_one_work+0x927/0x1ba0 kernel/workqueue.c:3214 process_scheduled_works kernel/workqueue.c:3319 [inline] worker_thread+0x6c8/0xf00 kernel/workqueue.c:3400 kthread+0x3b2/0x750 kernel/kthread.c:464 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 -> #0 ((wq_completion)ocfs2_wq){+.+.}-{0:0}: check_prev_add kernel/locking/lockdep.c:3163 [inline] check_prevs_add kernel/locking/lockdep.c:3282 [inline] validate_chain kernel/locking/lockdep.c:3906 [inline] __lock_acquire+0x249e/0x3c40 kernel/locking/lockdep.c:5228 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5851 touch_wq_lockdep_map+0xad/0x1c0 kernel/workqueue.c:3907 __flush_workqueue+0x129/0x1260 kernel/workqueue.c:3949 ocfs2_shutdown_local_alloc+0xbe/0xa10 fs/ocfs2/localalloc.c:380 ocfs2_dismount_volume+0x1f1/0xa00 fs/ocfs2/super.c:1822 generic_shutdown_super+0x156/0x390 fs/super.c:642 kill_block_super+0x3b/0x90 fs/super.c:1710 deactivate_locked_super+0xc1/0x1a0 fs/super.c:473 deactivate_super+0xde/0x100 fs/super.c:506 cleanup_mnt+0x222/0x450 fs/namespace.c:1413 task_work_run+0x151/0x250 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop kernel/entry/common.c:114 [inline] exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline] syscall_exit_to_user_mode+0x27b/0x2a0 kernel/entry/common.c:218 do_syscall_64+0xda/0x250 arch/x86/entry/common.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f 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#105 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&type->s_umount_key#105); lock((work_completion)(&journal->j_recovery_work)); lock(&type->s_umount_key#105); lock((wq_completion)ocfs2_wq); *** DEADLOCK *** 1 lock held by syz-executor/18759: #0: ffff8880564fc0e0 (&type->s_umount_key#105){++++}-{4:4}, at: __super_lock fs/super.c:56 [inline] #0: ffff8880564fc0e0 (&type->s_umount_key#105){++++}-{4:4}, at: __super_lock_excl fs/super.c:71 [inline] #0: ffff8880564fc0e0 (&type->s_umount_key#105){++++}-{4:4}, at: deactivate_super+0xd6/0x100 fs/super.c:505 stack backtrace: CPU: 0 UID: 0 PID: 18759 Comm: syz-executor Not tainted 6.14.0-rc7-syzkaller-00205-g586de92313fc #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_circular_bug+0x490/0x760 kernel/locking/lockdep.c:2076 check_noncircular+0x31a/0x400 kernel/locking/lockdep.c:2208 check_prev_add kernel/locking/lockdep.c:3163 [inline] check_prevs_add kernel/locking/lockdep.c:3282 [inline] validate_chain kernel/locking/lockdep.c:3906 [inline] __lock_acquire+0x249e/0x3c40 kernel/locking/lockdep.c:5228 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5851 touch_wq_lockdep_map+0xad/0x1c0 kernel/workqueue.c:3907 __flush_workqueue+0x129/0x1260 kernel/workqueue.c:3949 ocfs2_shutdown_local_alloc+0xbe/0xa10 fs/ocfs2/localalloc.c:380 ocfs2_dismount_volume+0x1f1/0xa00 fs/ocfs2/super.c:1822 generic_shutdown_super+0x156/0x390 fs/super.c:642 kill_block_super+0x3b/0x90 fs/super.c:1710 deactivate_locked_super+0xc1/0x1a0 fs/super.c:473 deactivate_super+0xde/0x100 fs/super.c:506 cleanup_mnt+0x222/0x450 fs/namespace.c:1413 task_work_run+0x151/0x250 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop kernel/entry/common.c:114 [inline] exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline] syscall_exit_to_user_mode+0x27b/0x2a0 kernel/entry/common.c:218 do_syscall_64+0xda/0x250 arch/x86/entry/common.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f0e8d78e497 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:00007fff7a694c18 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6 RAX: 0000000000000000 RBX: 00007f0e8d80e08c RCX: 00007f0e8d78e497 RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fff7a694cd0 RBP: 00007fff7a694cd0 R08: 0000000000000000 R09: 0000000000000000 R10: 00000000ffffffff R11: 0000000000000246 R12: 00007fff7a695d60 R13: 00007f0e8d80e08c R14: 000000000018bebc R15: 00007fff7a695da0 ocfs2: Unmounting device (7,3) on (node local)