JBD2: Ignoring recovery information on journal ocfs2: Mounting device (7,5) on (node local, slot 0) with ordered data mode. ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.5.151/5059 is trying to acquire lock: ffff0000f63e4da0 (&oi->ip_alloc_sem){++++}-{3:3}, at: ocfs2_read_virt_blocks+0x238/0x8f0 fs/ocfs2/extent_map.c:984 but task is already holding lock: ffff0000d63608e8 (&journal->j_trans_barrier){.+.+}-{3:3}, at: ocfs2_start_trans+0x374/0x6cc fs/ocfs2/journal.c:374 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&journal->j_trans_barrier){.+.+}-{3:3}: down_read+0x64/0x300 kernel/locking/rwsem.c:1520 ocfs2_start_trans+0x374/0x6cc fs/ocfs2/journal.c:374 ocfs2_mknod+0xd1c/0x2110 fs/ocfs2/namei.c:361 ocfs2_create+0x19c/0x4f8 fs/ocfs2/namei.c:674 lookup_open fs/namei.c:3490 [inline] open_last_lookups fs/namei.c:3558 [inline] path_openat+0xe18/0x26bc fs/namei.c:3788 do_filp_open+0x194/0x384 fs/namei.c:3818 do_sys_openat2+0x134/0x3f4 fs/open.c:1320 do_sys_open fs/open.c:1336 [inline] __do_sys_openat fs/open.c:1352 [inline] __se_sys_openat fs/open.c:1347 [inline] __arm64_sys_openat+0x118/0x14c fs/open.c:1347 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b4 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x130 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x128 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 (sb_internal#4){.+.+}-{0:0}: 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/0x6cc fs/ocfs2/journal.c:372 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+0x920/0x3a44 fs/ocfs2/aops.c:1670 ocfs2_write_begin+0x1b8/0x31c fs/ocfs2/aops.c:1904 generic_perform_write+0x234/0x4f4 mm/filemap.c:3862 __generic_file_write_iter+0x130/0x250 mm/filemap.c:3960 ocfs2_file_write_iter+0x138c/0x1c64 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+0x3ec/0x7f0 fs/read_write.c:584 ksys_write+0x12c/0x224 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/0x2b4 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x130 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x128 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 (&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+0x2880/0x6800 kernel/locking/lockdep.c:5049 lock_acquire+0x20c/0x63c kernel/locking/lockdep.c:5662 down_read+0x64/0x300 kernel/locking/rwsem.c:1520 ocfs2_read_virt_blocks+0x238/0x8f0 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+0x2e4/0x1d6c fs/ocfs2/dir.c:1091 ocfs2_rename+0x196c/0x30b4 fs/ocfs2/namei.c:1568 vfs_rename+0x95c/0xde0 fs/namei.c:4882 do_renameat2+0x744/0xa74 fs/namei.c:5035 __do_sys_renameat2 fs/namei.c:5068 [inline] __se_sys_renameat2 fs/namei.c:5065 [inline] __arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5065 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b4 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x130 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x128 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: &oi->ip_alloc_sem --> sb_internal#4 --> &journal->j_trans_barrier Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&journal->j_trans_barrier); lock(sb_internal#4); lock(&journal->j_trans_barrier); lock(&oi->ip_alloc_sem); *** DEADLOCK *** 8 locks held by syz.5.151/5059: #0: ffff0000dc5d0460 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:402 #1: ffff0000dc5d0748 (&type->s_vfs_rename_key#4){+.+.}-{3:3}, at: lock_rename fs/namei.c:3046 [inline] #1: ffff0000dc5d0748 (&type->s_vfs_rename_key#4){+.+.}-{3:3}, at: do_renameat2+0x308/0xa74 fs/namei.c:4974 #2: ffff0000f63e5108 (&sb->s_type->i_mutex_key#26/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline] #2: ffff0000f63e5108 (&sb->s_type->i_mutex_key#26/1){+.+.}-{3:3}, at: lock_two_directories fs/namei.c:-1 [inline] #2: ffff0000f63e5108 (&sb->s_type->i_mutex_key#26/1){+.+.}-{3:3}, at: lock_rename fs/namei.c:3047 [inline] #2: ffff0000f63e5108 (&sb->s_type->i_mutex_key#26/1){+.+.}-{3:3}, at: do_renameat2+0x384/0xa74 fs/namei.c:4974 #3: ffff0000f600d108 (&sb->s_type->i_mutex_key#26/5){+.+.}-{3:3}, at: lock_rename include/linux/fs.h:-1 [inline] #3: ffff0000f600d108 (&sb->s_type->i_mutex_key#26/5){+.+.}-{3:3}, at: do_renameat2+0x3b8/0xa74 fs/namei.c:4974 #4: ffff0000f600c2c8 (&sb->s_type->i_mutex_key#26/2){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline] #4: ffff0000f600c2c8 (&sb->s_type->i_mutex_key#26/2){+.+.}-{3:3}, at: vfs_rename+0x614/0xde0 fs/namei.c:4845 #5: ffff0000dc5d0650 (sb_internal#4){.+.+}-{0:0}, at: ocfs2_rename+0x1600/0x30b4 fs/ocfs2/namei.c:1488 #6: ffff0000d63608e8 (&journal->j_trans_barrier){.+.+}-{3:3}, at: ocfs2_start_trans+0x374/0x6cc fs/ocfs2/journal.c:374 #7: ffff0000dc80e990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0x1020/0x1280 fs/jbd2/transaction.c:461 stack backtrace: CPU: 1 PID: 5059 Comm: syz.5.151 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025 Call trace: dump_backtrace+0x1c0/0x1ec 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+0xf4/0x15c 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+0x264/0x2f8 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+0x2880/0x6800 kernel/locking/lockdep.c:5049 lock_acquire+0x20c/0x63c kernel/locking/lockdep.c:5662 down_read+0x64/0x300 kernel/locking/rwsem.c:1520 ocfs2_read_virt_blocks+0x238/0x8f0 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+0x2e4/0x1d6c fs/ocfs2/dir.c:1091 ocfs2_rename+0x196c/0x30b4 fs/ocfs2/namei.c:1568 vfs_rename+0x95c/0xde0 fs/namei.c:4882 do_renameat2+0x744/0xa74 fs/namei.c:5035 __do_sys_renameat2 fs/namei.c:5068 [inline] __se_sys_renameat2 fs/namei.c:5065 [inline] __arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5065 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b4 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x130 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x128 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