====================================================== WARNING: possible circular locking dependency detected 6.1.138-syzkaller #0 Not tainted ------------------------------------------------------ syz.3.385/5951 is trying to acquire lock: ffff0000e3ed2650 (sb_internal#4){.+.+}-{0:0}, at: ocfs2_write_begin_inline fs/ocfs2/aops.c:1481 [inline] ffff0000e3ed2650 (sb_internal#4){.+.+}-{0:0}, at: ocfs2_try_to_write_inline_data fs/ocfs2/aops.c:1584 [inline] ffff0000e3ed2650 (sb_internal#4){.+.+}-{0:0}, at: ocfs2_write_begin_nolock+0x1784/0x3ab4 fs/ocfs2/aops.c:1670 but task is already holding lock: ffff0001ffa56660 (&oi->ip_alloc_sem){++++}-{3:3}, at: ocfs2_write_begin+0x190/0x30c fs/ocfs2/aops.c:1902 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&oi->ip_alloc_sem){++++}-{3:3}: down_read+0x64/0x304 kernel/locking/rwsem.c:1520 ocfs2_read_virt_blocks+0x244/0x8e0 fs/ocfs2/extent_map.c:976 ocfs2_read_dir_block fs/ocfs2/dir.c:508 [inline] ocfs2_find_entry_el fs/ocfs2/dir.c:715 [inline] ocfs2_find_entry+0x318/0x1c5c fs/ocfs2/dir.c:1091 ocfs2_rename+0x1818/0x2edc fs/ocfs2/namei.c:1568 vfs_rename+0x954/0xdcc fs/namei.c:4874 do_renameat2+0x738/0xa54 fs/namei.c:5027 __do_sys_renameat2 fs/namei.c:5060 [inline] __se_sys_renameat2 fs/namei.c:5057 [inline] __arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5057 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 -> #2 (jbd2_handle){++++}-{0:0}: start_this_handle+0xfe0/0x122c fs/jbd2/transaction.c:463 jbd2__journal_start+0x288/0x51c fs/jbd2/transaction.c:520 jbd2_journal_start+0x3c/0x4c fs/jbd2/transaction.c:559 ocfs2_start_trans+0x380/0x6c4 fs/ocfs2/journal.c:354 ocfs2_local_alloc_slide_window fs/ocfs2/localalloc.c:1258 [inline] ocfs2_reserve_local_alloc_bits+0xb8c/0x278c fs/ocfs2/localalloc.c:668 ocfs2_reserve_clusters_with_limit+0x198/0x9e0 fs/ocfs2/suballoc.c:1162 ocfs2_reserve_clusters+0x3c/0x50 fs/ocfs2/suballoc.c:1223 ocfs2_mknod+0xc2c/0x1f18 fs/ocfs2/namei.c:354 ocfs2_mkdir+0x19c/0x4f0 fs/ocfs2/namei.c:657 vfs_mkdir+0x314/0x4d4 fs/namei.c:4106 do_mkdirat+0x1b4/0x3e0 fs/namei.c:4131 __do_sys_mkdirat fs/namei.c:4146 [inline] __se_sys_mkdirat fs/namei.c:4144 [inline] __arm64_sys_mkdirat+0x90/0xa8 fs/namei.c:4144 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 -> #1 (&journal->j_trans_barrier){.+.+}-{3:3}: down_read+0x64/0x304 kernel/locking/rwsem.c:1520 ocfs2_start_trans+0x374/0x6c4 fs/ocfs2/journal.c:352 ocfs2_local_alloc_slide_window fs/ocfs2/localalloc.c:1258 [inline] ocfs2_reserve_local_alloc_bits+0xb8c/0x278c fs/ocfs2/localalloc.c:668 ocfs2_reserve_clusters_with_limit+0x198/0x9e0 fs/ocfs2/suballoc.c:1162 ocfs2_reserve_clusters+0x3c/0x50 fs/ocfs2/suballoc.c:1223 ocfs2_mknod+0xc2c/0x1f18 fs/ocfs2/namei.c:354 ocfs2_mkdir+0x19c/0x4f0 fs/ocfs2/namei.c:657 vfs_mkdir+0x314/0x4d4 fs/namei.c:4106 do_mkdirat+0x1b4/0x3e0 fs/namei.c:4131 __do_sys_mkdirat fs/namei.c:4146 [inline] __se_sys_mkdirat fs/namei.c:4144 [inline] __arm64_sys_mkdirat+0x90/0xa8 fs/namei.c:4144 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 -> #0 (sb_internal#4){.+.+}-{0:0}: 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+0x293c/0x6544 kernel/locking/lockdep.c:5049 lock_acquire+0x20c/0x644 kernel/locking/lockdep.c:5662 percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1891 [inline] sb_start_intwrite include/linux/fs.h:2013 [inline] ocfs2_start_trans+0x20c/0x6c4 fs/ocfs2/journal.c:350 ocfs2_write_begin_inline fs/ocfs2/aops.c:1481 [inline] ocfs2_try_to_write_inline_data fs/ocfs2/aops.c:1584 [inline] ocfs2_write_begin_nolock+0x1784/0x3ab4 fs/ocfs2/aops.c:1670 ocfs2_write_begin+0x1b4/0x30c fs/ocfs2/aops.c:1904 generic_perform_write+0x230/0x4b0 mm/filemap.c:3846 __generic_file_write_iter+0x168/0x37c mm/filemap.c:3974 ocfs2_file_write_iter+0x1300/0x1bf4 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+0x5ac/0x7c4 fs/read_write.c:584 ksys_write+0x120/0x210 fs/read_write.c:637 __do_sys_write fs/read_write.c:649 [inline] __se_sys_write fs/read_write.c:646 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:646 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 other info that might help us debug this: Chain exists of: sb_internal#4 --> jbd2_handle --> &oi->ip_alloc_sem Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&oi->ip_alloc_sem); lock(jbd2_handle); lock(&oi->ip_alloc_sem); lock(sb_internal#4); *** DEADLOCK *** 4 locks held by syz.3.385/5951: #0: ffff0000d4b46868 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x114/0x16c fs/file.c:1040 #1: ffff0000e3ed2460 (sb_writers#17){.+.+}-{0:0}, at: vfs_write+0x23c/0x7c4 fs/read_write.c:580 #2: ffff0001ffa569c8 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #2: ffff0001ffa569c8 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: ocfs2_file_write_iter+0x3a4/0x1bf4 fs/ocfs2/file.c:2399 #3: ffff0001ffa56660 (&oi->ip_alloc_sem){++++}-{3:3}, at: ocfs2_write_begin+0x190/0x30c fs/ocfs2/aops.c:1902 stack backtrace: CPU: 1 PID: 5951 Comm: syz.3.385 Not tainted 6.1.138-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025 Call trace: dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165 __dump_stack+0x30/0x40 lib/dump_stack.c:88 dump_stack_lvl+0xf8/0x160 lib/dump_stack.c:106 dump_stack+0x1c/0x5c lib/dump_stack.c:113 print_circular_bug+0x148/0x1b0 kernel/locking/lockdep.c:2048 check_noncircular+0x240/0x2d4 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+0x293c/0x6544 kernel/locking/lockdep.c:5049 lock_acquire+0x20c/0x644 kernel/locking/lockdep.c:5662 percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1891 [inline] sb_start_intwrite include/linux/fs.h:2013 [inline] ocfs2_start_trans+0x20c/0x6c4 fs/ocfs2/journal.c:350 ocfs2_write_begin_inline fs/ocfs2/aops.c:1481 [inline] ocfs2_try_to_write_inline_data fs/ocfs2/aops.c:1584 [inline] ocfs2_write_begin_nolock+0x1784/0x3ab4 fs/ocfs2/aops.c:1670 ocfs2_write_begin+0x1b4/0x30c fs/ocfs2/aops.c:1904 generic_perform_write+0x230/0x4b0 mm/filemap.c:3846 __generic_file_write_iter+0x168/0x37c mm/filemap.c:3974 ocfs2_file_write_iter+0x1300/0x1bf4 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+0x5ac/0x7c4 fs/read_write.c:584 ksys_write+0x120/0x210 fs/read_write.c:637 __do_sys_write fs/read_write.c:649 [inline] __se_sys_write fs/read_write.c:646 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:646 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 device syzkaller1 entered promiscuous mode