====================================================== WARNING: possible circular locking dependency detected 6.14.0-rc1-syzkaller-00020-g0de63bb7d919 #0 Not tainted ------------------------------------------------------ syz-executor/6614 is trying to acquire lock: ffff88802a029148 ((wq_completion)ocfs2_wq){+.+.}-{0:0}, at: touch_wq_lockdep_map+0xb1/0x170 kernel/workqueue.c:3905 but task is already holding lock: ffff8880646240e0 (&type->s_umount_key#68){++++}-{4:4}, at: __super_lock fs/super.c:56 [inline] ffff8880646240e0 (&type->s_umount_key#68){++++}-{4:4}, at: __super_lock_excl fs/super.c:71 [inline] ffff8880646240e0 (&type->s_umount_key#68){++++}-{4:4}, at: deactivate_super+0xb5/0xf0 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#68){++++}-{4:4}: lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5851 down_read+0xb1/0xa40 kernel/locking/rwsem.c:1524 ocfs2_finish_quota_recovery+0x15c/0x22a0 fs/ocfs2/quota_local.c:603 ocfs2_complete_recovery+0x17c1/0x25c0 fs/ocfs2/journal.c:1357 process_one_work kernel/workqueue.c:3236 [inline] process_scheduled_works+0xa66/0x1840 kernel/workqueue.c:3317 worker_thread+0x870/0xd30 kernel/workqueue.c:3398 kthread+0x7a9/0x920 kernel/kthread.c:464 ret_from_fork+0x4b/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}: lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5851 process_one_work kernel/workqueue.c:3212 [inline] process_scheduled_works+0x994/0x1840 kernel/workqueue.c:3317 worker_thread+0x870/0xd30 kernel/workqueue.c:3398 kthread+0x7a9/0x920 kernel/kthread.c:464 ret_from_fork+0x4b/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+0x18ef/0x5920 kernel/locking/lockdep.c:3906 __lock_acquire+0x1397/0x2100 kernel/locking/lockdep.c:5228 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5851 touch_wq_lockdep_map+0xc7/0x170 kernel/workqueue.c:3905 __flush_workqueue+0x14a/0x1280 kernel/workqueue.c:3947 ocfs2_shutdown_local_alloc+0x109/0xa90 fs/ocfs2/localalloc.c:380 ocfs2_dismount_volume+0x202/0x910 fs/ocfs2/super.c:1822 generic_shutdown_super+0x139/0x2d0 fs/super.c:642 kill_block_super+0x44/0x90 fs/super.c:1710 deactivate_locked_super+0xc4/0x130 fs/super.c:473 cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1413 task_work_run+0x24f/0x310 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+0x13f/0x340 kernel/entry/common.c:218 do_syscall_64+0x100/0x230 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#68 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&type->s_umount_key#68); lock((work_completion)(&journal->j_recovery_work)); lock(&type->s_umount_key#68); lock((wq_completion)ocfs2_wq); *** DEADLOCK *** 1 lock held by syz-executor/6614: #0: ffff8880646240e0 (&type->s_umount_key#68){++++}-{4:4}, at: __super_lock fs/super.c:56 [inline] #0: ffff8880646240e0 (&type->s_umount_key#68){++++}-{4:4}, at: __super_lock_excl fs/super.c:71 [inline] #0: ffff8880646240e0 (&type->s_umount_key#68){++++}-{4:4}, at: deactivate_super+0xb5/0xf0 fs/super.c:505 stack backtrace: CPU: 1 UID: 0 PID: 6614 Comm: syz-executor Not tainted 6.14.0-rc1-syzkaller-00020-g0de63bb7d919 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_circular_bug+0x13a/0x1b0 kernel/locking/lockdep.c:2076 check_noncircular+0x36a/0x4a0 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+0x18ef/0x5920 kernel/locking/lockdep.c:3906 __lock_acquire+0x1397/0x2100 kernel/locking/lockdep.c:5228 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5851 touch_wq_lockdep_map+0xc7/0x170 kernel/workqueue.c:3905 __flush_workqueue+0x14a/0x1280 kernel/workqueue.c:3947 ocfs2_shutdown_local_alloc+0x109/0xa90 fs/ocfs2/localalloc.c:380 ocfs2_dismount_volume+0x202/0x910 fs/ocfs2/super.c:1822 generic_shutdown_super+0x139/0x2d0 fs/super.c:642 kill_block_super+0x44/0x90 fs/super.c:1710 deactivate_locked_super+0xc4/0x130 fs/super.c:473 cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1413 task_work_run+0x24f/0x310 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+0x13f/0x340 kernel/entry/common.c:218 do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f47c7f8e0d7 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:00007ffedc97d238 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f47c7f8e0d7 RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffedc97d2f0 RBP: 00007ffedc97d2f0 R08: 0000000000000000 R09: 0000000000000000 R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffedc97e380 R13: 00007f47c800e08c R14: 0000000000036e28 R15: 00007ffedc97e3c0 ocfs2: Unmounting device (7,7) on (node local)