====================================================== WARNING: possible circular locking dependency detected 6.14.0-rc6-syzkaller-00103-g4003c9e78778 #0 Not tainted ------------------------------------------------------ syz-executor/9043 is trying to acquire lock: ffff8880360ad100 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#7){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:877 [inline] ffff8880360ad100 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#7){+.+.}-{4:4}, at: __ocfs2_flush_truncate_log+0x32e/0x1150 fs/ocfs2/alloc.c:6046 but task is already holding lock: ffff8880360b3480 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#8){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:877 [inline] ffff8880360b3480 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#8){+.+.}-{4:4}, at: ocfs2_flush_truncate_log+0x42/0x70 fs/ocfs2/alloc.c:6075 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#8){+.+.}-{4:4}: down_write+0x93/0x200 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:877 [inline] ocfs2_move_extent+0x6e2/0x1800 fs/ocfs2/move_extents.c:640 __ocfs2_move_extents_range fs/ocfs2/move_extents.c:860 [inline] ocfs2_move_extents+0xd73/0x19a0 fs/ocfs2/move_extents.c:927 ocfs2_ioctl_move_extents+0x54f/0xb30 fs/ocfs2/move_extents.c:1053 ocfs2_ioctl+0x3c4/0x6f0 fs/ocfs2/ioctl.c:946 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:906 [inline] __se_sys_ioctl fs/ioctl.c:892 [inline] __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:892 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#7){+.+.}-{4:4}: 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 down_write+0x93/0x200 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:877 [inline] __ocfs2_flush_truncate_log+0x32e/0x1150 fs/ocfs2/alloc.c:6046 ocfs2_flush_truncate_log+0x4a/0x70 fs/ocfs2/alloc.c:6076 ocfs2_sync_fs+0x1c8/0x3d0 fs/ocfs2/super.c:406 sync_filesystem+0x1cf/0x290 fs/sync.c:66 generic_shutdown_super+0x74/0x390 fs/super.c:621 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: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#8); lock(&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#7); lock(&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#8); lock(&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#7); *** DEADLOCK *** 2 locks held by syz-executor/9043: #0: ffff88804002c0e0 (&type->s_umount_key#73){+.+.}-{4:4}, at: __super_lock fs/super.c:56 [inline] #0: ffff88804002c0e0 (&type->s_umount_key#73){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:71 [inline] #0: ffff88804002c0e0 (&type->s_umount_key#73){+.+.}-{4:4}, at: deactivate_super+0xd6/0x100 fs/super.c:505 #1: ffff8880360b3480 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#8){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:877 [inline] #1: ffff8880360b3480 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#8){+.+.}-{4:4}, at: ocfs2_flush_truncate_log+0x42/0x70 fs/ocfs2/alloc.c:6075 stack backtrace: CPU: 1 UID: 0 PID: 9043 Comm: syz-executor Not tainted 6.14.0-rc6-syzkaller-00103-g4003c9e78778 #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 down_write+0x93/0x200 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:877 [inline] __ocfs2_flush_truncate_log+0x32e/0x1150 fs/ocfs2/alloc.c:6046 ocfs2_flush_truncate_log+0x4a/0x70 fs/ocfs2/alloc.c:6076 ocfs2_sync_fs+0x1c8/0x3d0 fs/ocfs2/super.c:406 sync_filesystem+0x1cf/0x290 fs/sync.c:66 generic_shutdown_super+0x74/0x390 fs/super.c:621 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:0x7f8811b8e497 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:00007ffe68fa12c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6 RAX: 0000000000000000 RBX: 00007f8811c0e08c RCX: 00007f8811b8e497 RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffe68fa1380 RBP: 00007ffe68fa1380 R08: 0000000000000000 R09: 0000000000000000 R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffe68fa2410 R13: 00007f8811c0e08c R14: 0000000000086689 R15: 00007ffe68fa2450 ocfs2: Unmounting device (7,4) on (node local) EXT4-fs (loop4): unmounting filesystem 00000000-0000-0000-0000-000000000000.