JBD2: Ignoring recovery information on journal ocfs2: Mounting device (7,4) on (node local, slot 0) with ordered data mode. ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.4.610/6806 is trying to acquire lock: ffff0000f5ea0660 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_read_virt_blocks+0x23c/0x8c8 fs/ocfs2/extent_map.c:984 but task is already holding lock: ffff0000ca0bf0e8 (&journal->j_trans_barrier){.+.+}-{3:3}, at: ocfs2_start_trans+0x38c/0x6f4 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+0x38c/0x6f4 fs/ocfs2/journal.c:374 ocfs2_mknod+0xd2c/0x218c fs/ocfs2/namei.c:361 ocfs2_create+0x19c/0x51c fs/ocfs2/namei.c:674 lookup_open fs/namei.c:3490 [inline] open_last_lookups fs/namei.c:3558 [inline] path_openat+0xda8/0x27a0 fs/namei.c:3788 do_filp_open+0x198/0x38c fs/namei.c:3818 do_sys_openat2+0x134/0x3fc 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+0x11c/0x150 fs/open.c:1347 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x5c/0x134 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#2){.+.+}-{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/0x6f4 fs/ocfs2/journal.c:372 ocfs2_zero_start_ordered_transaction fs/ocfs2/file.c:719 [inline] ocfs2_write_zero_page fs/ocfs2/file.c:765 [inline] ocfs2_zero_extend_range fs/ocfs2/file.c:949 [inline] ocfs2_zero_extend+0x7d0/0x24f0 fs/ocfs2/file.c:994 ocfs2_extend_no_holes+0x1f4/0x438 fs/ocfs2/file.c:1040 ocfs2_expand_nonsparse_inode+0x134/0x3b0 fs/ocfs2/aops.c:1623 ocfs2_write_begin_nolock+0xea4/0x3a80 fs/ocfs2/aops.c:1689 ocfs2_write_begin+0x1b4/0x318 fs/ocfs2/aops.c:1906 generic_perform_write+0x240/0x508 mm/filemap.c:3862 __generic_file_write_iter+0x130/0x250 mm/filemap.c:3960 ocfs2_file_write_iter+0x13ac/0x1cd0 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+0x3c8/0x7c8 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] __arm64_sys_pwrite64+0x178/0x210 fs/read_write.c:706 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x5c/0x134 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 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3095 [inline] check_prevs_add kernel/locking/lockdep.c:3214 [inline] validate_chain kernel/locking/lockdep.c:3830 [inline] __lock_acquire+0x2808/0x6634 kernel/locking/lockdep.c:5063 lock_acquire+0x20c/0x638 kernel/locking/lockdep.c:5676 down_read+0x64/0x300 kernel/locking/rwsem.c:1520 ocfs2_read_virt_blocks+0x23c/0x8c8 fs/ocfs2/extent_map.c:984 ocfs2_read_dir_block+0xd4/0x46c fs/ocfs2/dir.c:508 ocfs2_dir_foreach_blk_el fs/ocfs2/dir.c:1842 [inline] ocfs2_dir_foreach_blk+0x228/0x16a4 fs/ocfs2/dir.c:1928 ocfs2_dir_foreach+0x168/0x1c0 fs/ocfs2/dir.c:1938 ocfs2_empty_dir+0xf4/0x590 fs/ocfs2/dir.c:2156 ocfs2_rename+0x1c64/0x3160 fs/ocfs2/namei.c:1499 vfs_rename+0xb08/0xe3c fs/namei.c:4882 do_renameat2+0x760/0xaa4 fs/namei.c:5035 __do_sys_renameat2 fs/namei.c:5068 [inline] __se_sys_renameat2 fs/namei.c:5065 [inline] __arm64_sys_renameat2+0xe8/0x104 fs/namei.c:5065 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x5c/0x134 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: &ocfs2_file_ip_alloc_sem_key --> sb_internal#2 --> &journal->j_trans_barrier Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&journal->j_trans_barrier); lock(sb_internal#2); lock(&journal->j_trans_barrier); lock(&ocfs2_file_ip_alloc_sem_key); *** DEADLOCK *** 7 locks held by syz.4.610/6806: #0: ffff0000dc270460 (sb_writers#16){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:402 #1: ffff0000fd1442c8 (&type->i_mutex_dir_key#11/1){+.+.}-{3:3}, at: lock_rename include/linux/fs.h:-1 [inline] #1: ffff0000fd1442c8 (&type->i_mutex_dir_key#11/1){+.+.}-{3:3}, at: do_renameat2+0x3c4/0xaa4 fs/namei.c:4974 #2: ffff0000f5ea09c8 (&sb->s_type->i_mutex_key#22){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #2: ffff0000f5ea09c8 (&sb->s_type->i_mutex_key#22){+.+.}-{3:3}, at: vfs_rename+0x6a8/0xe3c fs/namei.c:4847 #3: ffff0000f5c1c2c8 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #3: ffff0000f5c1c2c8 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]){+.+.}-{3:3}, at: ocfs2_lookup_lock_orphan_dir+0xc8/0x288 fs/ocfs2/namei.c:2116 #4: ffff0000dc270650 (sb_internal#2){.+.+}-{0:0}, at: ocfs2_rename+0x1638/0x3160 fs/ocfs2/namei.c:1488 #5: ffff0000ca0bf0e8 (&journal->j_trans_barrier){.+.+}-{3:3}, at: ocfs2_start_trans+0x38c/0x6f4 fs/ocfs2/journal.c:374 #6: ffff0000d540c990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0xfec/0x125c fs/jbd2/transaction.c:461 stack backtrace: CPU: 0 PID: 6806 Comm: syz.4.610 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/02/2026 Call trace: dump_backtrace+0x1c4/0x1f0 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:3095 [inline] check_prevs_add kernel/locking/lockdep.c:3214 [inline] validate_chain kernel/locking/lockdep.c:3830 [inline] __lock_acquire+0x2808/0x6634 kernel/locking/lockdep.c:5063 lock_acquire+0x20c/0x638 kernel/locking/lockdep.c:5676 down_read+0x64/0x300 kernel/locking/rwsem.c:1520 ocfs2_read_virt_blocks+0x23c/0x8c8 fs/ocfs2/extent_map.c:984 ocfs2_read_dir_block+0xd4/0x46c fs/ocfs2/dir.c:508 ocfs2_dir_foreach_blk_el fs/ocfs2/dir.c:1842 [inline] ocfs2_dir_foreach_blk+0x228/0x16a4 fs/ocfs2/dir.c:1928 ocfs2_dir_foreach+0x168/0x1c0 fs/ocfs2/dir.c:1938 ocfs2_empty_dir+0xf4/0x590 fs/ocfs2/dir.c:2156 ocfs2_rename+0x1c64/0x3160 fs/ocfs2/namei.c:1499 vfs_rename+0xb08/0xe3c fs/namei.c:4882 do_renameat2+0x760/0xaa4 fs/namei.c:5035 __do_sys_renameat2 fs/namei.c:5068 [inline] __se_sys_renameat2 fs/namei.c:5065 [inline] __arm64_sys_renameat2+0xe8/0x104 fs/namei.c:5065 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x5c/0x134 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