======================================================
WARNING: possible circular locking dependency detected
6.14.0-rc7-syzkaller-ga2392f333575 #0 Not tainted
------------------------------------------------------
syz-executor/6448 is trying to acquire lock:
ffff0000d1e3d148 ((wq_completion)ocfs2_wq){+.+.}-{0:0}, at: touch_wq_lockdep_map+0x70/0x164 kernel/workqueue.c:3904

but task is already holding lock:
ffff0000dfad20e0 (&type->s_umount_key#74){++++}-{4:4}, at: __super_lock fs/super.c:56 [inline]
ffff0000dfad20e0 (&type->s_umount_key#74){++++}-{4:4}, at: __super_lock_excl fs/super.c:71 [inline]
ffff0000dfad20e0 (&type->s_umount_key#74){++++}-{4:4}, at: deactivate_super+0xd8/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#74){++++}-{4:4}:
       down_read+0x58/0x2fc kernel/locking/rwsem.c:1524
       ocfs2_finish_quota_recovery+0x198/0x1f94 fs/ocfs2/quota_local.c:603
       ocfs2_complete_recovery+0x1610/0x2368 fs/ocfs2/journal.c:1357
       process_one_work+0x810/0x1638 kernel/workqueue.c:3238
       process_scheduled_works kernel/workqueue.c:3319 [inline]
       worker_thread+0x97c/0xeec kernel/workqueue.c:3400
       kthread+0x65c/0x7b0 kernel/kthread.c:464
       ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:862

-> #1 ((work_completion)(&journal->j_recovery_work)){+.+.}-{0:0}:
       process_one_work+0x730/0x1638 kernel/workqueue.c:3214
       process_scheduled_works kernel/workqueue.c:3319 [inline]
       worker_thread+0x97c/0xeec kernel/workqueue.c:3400
       kthread+0x65c/0x7b0 kernel/kthread.c:464
       ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:862

-> #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+0x34f0/0x7904 kernel/locking/lockdep.c:5228
       lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5851
       touch_wq_lockdep_map+0xa8/0x164 kernel/workqueue.c:3907
       __flush_workqueue+0x120/0x1234 kernel/workqueue.c:3949
       ocfs2_shutdown_local_alloc+0x104/0x8d8 fs/ocfs2/localalloc.c:380
       ocfs2_dismount_volume+0x1f4/0x920 fs/ocfs2/super.c:1822
       ocfs2_put_super+0xec/0x368 fs/ocfs2/super.c:1553
       generic_shutdown_super+0x12c/0x2bc fs/super.c:642
       kill_block_super+0x44/0x90 fs/super.c:1710
       deactivate_locked_super+0xc4/0x12c fs/super.c:473
       deactivate_super+0xe0/0x100 fs/super.c:506
       cleanup_mnt+0x34c/0x3dc fs/namespace.c:1413
       __cleanup_mnt+0x20/0x30 fs/namespace.c:1420
       task_work_run+0x230/0x2e0 kernel/task_work.c:227
       resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
       do_notify_resume+0x178/0x1f4 arch/arm64/kernel/entry-common.c:151
       exit_to_user_mode_prepare arch/arm64/kernel/entry-common.c:169 [inline]
       exit_to_user_mode arch/arm64/kernel/entry-common.c:178 [inline]
       el0_svc+0xac/0x168 arch/arm64/kernel/entry-common.c:745
       el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762
       el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600

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#74

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&type->s_umount_key#74);
                               lock((work_completion)(&journal->j_recovery_work));
                               lock(&type->s_umount_key#74);
  lock((wq_completion)ocfs2_wq);

 *** DEADLOCK ***

1 lock held by syz-executor/6448:
 #0: 
ffff0000dfad20e0 (&type->s_umount_key#74
){++++}-{4:4}
, at: __super_lock fs/super.c:56 [inline]
, at: __super_lock_excl fs/super.c:71 [inline]
, at: deactivate_super+0xd8/0x100 fs/super.c:505

stack backtrace:
CPU: 0 UID: 0 PID: 6448 Comm: syz-executor Not tainted 6.14.0-rc7-syzkaller-ga2392f333575 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call trace:
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:466 (C)
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:120
 dump_stack+0x1c/0x28 lib/dump_stack.c:129
 print_circular_bug+0x154/0x1c0 kernel/locking/lockdep.c:2076
 check_noncircular+0x310/0x404 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+0x34f0/0x7904 kernel/locking/lockdep.c:5228
 lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5851
 touch_wq_lockdep_map+0xa8/0x164 kernel/workqueue.c:3907
 __flush_workqueue+0x120/0x1234 kernel/workqueue.c:3949
 ocfs2_shutdown_local_alloc+0x104/0x8d8 fs/ocfs2/localalloc.c:380
 ocfs2_dismount_volume+0x1f4/0x920 fs/ocfs2/super.c:1822
 ocfs2_put_super+0xec/0x368 fs/ocfs2/super.c:1553
 generic_shutdown_super+0x12c/0x2bc fs/super.c:642
 kill_block_super+0x44/0x90 fs/super.c:1710
 deactivate_locked_super+0xc4/0x12c fs/super.c:473
 deactivate_super+0xe0/0x100 fs/super.c:506
 cleanup_mnt+0x34c/0x3dc fs/namespace.c:1413
 __cleanup_mnt+0x20/0x30 fs/namespace.c:1420
 task_work_run+0x230/0x2e0 kernel/task_work.c:227
 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
 do_notify_resume+0x178/0x1f4 arch/arm64/kernel/entry-common.c:151
 exit_to_user_mode_prepare arch/arm64/kernel/entry-common.c:169 [inline]
 exit_to_user_mode arch/arm64/kernel/entry-common.c:178 [inline]
 el0_svc+0xac/0x168 arch/arm64/kernel/entry-common.c:745
 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600
ocfs2: Unmounting device (7,0) on (node local)
BTRFS info (device loop0): last unmount of filesystem 1b93cb2a-192d-4824-ba24-a034f68e2fcd