ocfs2: Mounting device (7,2) on (node local, slot 0) with ordered data mode. ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.2.59/4632 is trying to acquire lock: ffff88804e8394a0 (&oi->ip_alloc_sem){++++}-{3:3}, at: ocfs2_read_virt_blocks+0x25d/0x970 fs/ocfs2/extent_map.c:984 but task is already holding lock: ffff88805342c990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0x200f/0x2230 fs/jbd2/transaction.c:463 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (jbd2_handle){++++}-{0:0}: jbd2_log_wait_commit+0x16c/0x4c0 fs/jbd2/journal.c:694 ocfs2_try_to_free_truncate_log+0x316/0x350 fs/ocfs2/alloc.c:6142 ocfs2_write_begin_nolock+0x3437/0x44f0 fs/ocfs2/aops.c:1870 ocfs2_write_begin+0x1c2/0x320 fs/ocfs2/aops.c:1904 generic_perform_write+0x2fa/0x5c0 mm/filemap.c:3862 __generic_file_write_iter+0x148/0x2a0 mm/filemap.c:3960 ocfs2_file_write_iter+0x1660/0x1f00 fs/ocfs2/file.c:2469 call_write_iter include/linux/fs.h:2265 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x4b1/0xa30 fs/read_write.c:584 ksys_pwrite64 fs/read_write.c:699 [inline] __do_sys_pwrite64 fs/read_write.c:709 [inline] __se_sys_pwrite64 fs/read_write.c:706 [inline] __x64_sys_pwrite64+0x197/0x220 fs/read_write.c:706 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #0 (&oi->ip_alloc_sem){++++}-{3:3}: 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+0x2d07/0x7d10 kernel/locking/lockdep.c:5049 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5662 down_read+0x42/0x2d0 kernel/locking/rwsem.c:1520 ocfs2_read_virt_blocks+0x25d/0x970 fs/ocfs2/extent_map.c:984 ocfs2_read_dir_block fs/ocfs2/dir.c:508 [inline] ocfs2_find_entry_el fs/ocfs2/dir.c:715 [inline] ocfs2_find_entry+0x3c1/0x2180 fs/ocfs2/dir.c:1091 ocfs2_rename+0x1e72/0x3950 fs/ocfs2/namei.c:1568 vfs_rename+0xbe1/0x1100 fs/namei.c:4882 do_renameat2+0x8e5/0xce0 fs/namei.c:5035 __do_sys_rename fs/namei.c:5081 [inline] __se_sys_rename fs/namei.c:5079 [inline] __x64_sys_rename+0x82/0x90 fs/namei.c:5079 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(jbd2_handle); lock(&oi->ip_alloc_sem); lock(jbd2_handle); lock(&oi->ip_alloc_sem); *** DEADLOCK *** 8 locks held by syz.2.59/4632: #0: ffff888029b82460 (sb_writers#23){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:402 #1: ffff888029b82748 (&type->s_vfs_rename_key){+.+.}-{3:3}, at: lock_rename fs/namei.c:3046 [inline] #1: ffff888029b82748 (&type->s_vfs_rename_key){+.+.}-{3:3}, at: do_renameat2+0x363/0xce0 fs/namei.c:4974 #2: ffff888054b53488 (&type->i_mutex_dir_key#17/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline] #2: ffff888054b53488 (&type->i_mutex_dir_key#17/1){+.+.}-{3:3}, at: lock_two_directories fs/namei.c:-1 [inline] #2: ffff888054b53488 (&type->i_mutex_dir_key#17/1){+.+.}-{3:3}, at: lock_rename fs/namei.c:3047 [inline] #2: ffff888054b53488 (&type->i_mutex_dir_key#17/1){+.+.}-{3:3}, at: do_renameat2+0x3fa/0xce0 fs/namei.c:4974 #3: ffff88804e839808 (&sb->s_type->i_mutex_key#30/5){+.+.}-{3:3}, at: lock_rename include/linux/fs.h:-1 [inline] #3: ffff88804e839808 (&sb->s_type->i_mutex_key#30/5){+.+.}-{3:3}, at: do_renameat2+0x435/0xce0 fs/namei.c:4974 #4: ffff88804e866d88 (&sb->s_type->i_mutex_key#30/2){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline] #4: ffff88804e866d88 (&sb->s_type->i_mutex_key#30/2){+.+.}-{3:3}, at: vfs_rename+0x792/0x1100 fs/namei.c:4845 #5: ffff888029b82650 (sb_internal#4){.+.+}-{0:0}, at: ocfs2_rename+0x1a48/0x3950 fs/ocfs2/namei.c:1488 #6: ffff8880552394e8 (&journal->j_trans_barrier){.+.+}-{3:3}, at: ocfs2_start_trans+0x3a4/0x6f0 fs/ocfs2/journal.c:374 #7: ffff88805342c990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0x200f/0x2230 fs/jbd2/transaction.c:463 stack backtrace: CPU: 1 PID: 4632 Comm: syz.2.59 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026 Call Trace: dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106 check_noncircular+0x296/0x330 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+0x2d07/0x7d10 kernel/locking/lockdep.c:5049 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5662 down_read+0x42/0x2d0 kernel/locking/rwsem.c:1520 ocfs2_read_virt_blocks+0x25d/0x970 fs/ocfs2/extent_map.c:984 ocfs2_read_dir_block fs/ocfs2/dir.c:508 [inline] ocfs2_find_entry_el fs/ocfs2/dir.c:715 [inline] ocfs2_find_entry+0x3c1/0x2180 fs/ocfs2/dir.c:1091 ocfs2_rename+0x1e72/0x3950 fs/ocfs2/namei.c:1568 vfs_rename+0xbe1/0x1100 fs/namei.c:4882 do_renameat2+0x8e5/0xce0 fs/namei.c:5035 __do_sys_rename fs/namei.c:5081 [inline] __se_sys_rename fs/namei.c:5079 [inline] __x64_sys_rename+0x82/0x90 fs/namei.c:5079 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7ff30f59c799 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ff3104e1028 EFLAGS: 00000246 ORIG_RAX: 0000000000000052 RAX: ffffffffffffffda RBX: 00007ff30f815fa0 RCX: 00007ff30f59c799 RDX: 0000000000000000 RSI: 0000200000000080 RDI: 0000200000000100 RBP: 00007ff30f632c99 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ff30f816038 R14: 00007ff30f815fa0 R15: 00007ffc23aab4e8