JBD2: Ignoring recovery information on journal ocfs2: Mounting device (7,2) on (node local, slot 0) with ordered data mode. ====================================================== WARNING: possible circular locking dependency detected 6.11.0-rc7-syzkaller-g5f5673607153 #0 Not tainted ------------------------------------------------------ syz.2.330/8063 is trying to acquire lock: ffff0001003015a8 (&osb->system_file_mutex){+.+.}-{3:3}, at: ocfs2_get_system_file_inode+0x180/0x6d8 fs/ocfs2/sysfile.c:101 but task is already holding lock: ffff0000ef6ab120 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_write_begin+0x178/0x38c fs/ocfs2/aops.c:1901 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}: down_read+0x58/0x2fc kernel/locking/rwsem.c:1526 ocfs2_read_virt_blocks+0x294/0x980 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+0x398/0x247c fs/ocfs2/dir.c:1080 ocfs2_find_files_on_disk+0x11c/0x3e8 fs/ocfs2/dir.c:1980 ocfs2_lookup_ino_from_name+0xb8/0x1d4 fs/ocfs2/dir.c:2002 _ocfs2_get_system_file_inode fs/ocfs2/sysfile.c:136 [inline] ocfs2_get_system_file_inode+0x2e0/0x6d8 fs/ocfs2/sysfile.c:112 ocfs2_init_global_system_inodes+0x2bc/0x618 fs/ocfs2/super.c:457 ocfs2_initialize_super fs/ocfs2/super.c:2250 [inline] ocfs2_fill_super+0x2590/0x4740 fs/ocfs2/super.c:994 mount_bdev+0x1d4/0x2a0 fs/super.c:1679 ocfs2_mount+0x44/0x58 fs/ocfs2/super.c:1188 legacy_get_tree+0xd4/0x16c fs/fs_context.c:662 vfs_get_tree+0x90/0x28c fs/super.c:1800 do_new_mount+0x278/0x900 fs/namespace.c:3472 path_mount+0x590/0xe04 fs/namespace.c:3799 do_mount fs/namespace.c:3812 [inline] __do_sys_mount fs/namespace.c:4020 [inline] __se_sys_mount fs/namespace.c:3997 [inline] __arm64_sys_mount+0x45c/0x5a8 fs/namespace.c:3997 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598 -> #0 (&osb->system_file_mutex){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3133 [inline] check_prevs_add kernel/locking/lockdep.c:3252 [inline] validate_chain kernel/locking/lockdep.c:3868 [inline] __lock_acquire+0x33d8/0x779c kernel/locking/lockdep.c:5142 lock_acquire+0x240/0x728 kernel/locking/lockdep.c:5759 __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:608 __mutex_lock kernel/locking/mutex.c:752 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:804 ocfs2_get_system_file_inode+0x180/0x6d8 fs/ocfs2/sysfile.c:101 ocfs2_reserve_local_alloc_bits+0xe4/0x247c fs/ocfs2/localalloc.c:627 ocfs2_reserve_clusters_with_limit+0x194/0xabc fs/ocfs2/suballoc.c:1166 ocfs2_reserve_clusters fs/ocfs2/suballoc.c:1227 [inline] ocfs2_lock_allocators+0x294/0x584 fs/ocfs2/suballoc.c:2746 ocfs2_write_begin_nolock+0x22cc/0x3e6c fs/ocfs2/aops.c:1739 ocfs2_write_begin+0x1ac/0x38c fs/ocfs2/aops.c:1903 generic_perform_write+0x2e8/0x8e0 mm/filemap.c:4019 __generic_file_write_iter+0xfc/0x204 mm/filemap.c:4121 ocfs2_file_write_iter+0x1520/0x1e10 fs/ocfs2/file.c:2455 new_sync_write fs/read_write.c:497 [inline] vfs_write+0x940/0xc80 fs/read_write.c:590 ksys_write+0x15c/0x26c fs/read_write.c:643 __do_sys_write fs/read_write.c:655 [inline] __se_sys_write fs/read_write.c:652 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:652 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ocfs2_file_ip_alloc_sem_key); lock(&osb->system_file_mutex); lock(&ocfs2_file_ip_alloc_sem_key); lock(&osb->system_file_mutex); *** DEADLOCK *** 4 locks held by syz.2.330/8063: #0: ffff0000ce9b4fc8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x218/0x2a4 fs/file.c:1187 #1: ffff0000e1042420 (sb_writers#16){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2882 [inline] #1: ffff0000e1042420 (sb_writers#16){.+.+}-{0:0}, at: vfs_write+0x368/0xc80 fs/read_write.c:586 #2: ffff0000ef6ab480 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:800 [inline] #2: ffff0000ef6ab480 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ocfs2_file_write_iter+0x390/0x1e10 fs/ocfs2/file.c:2387 #3: ffff0000ef6ab120 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_write_begin+0x178/0x38c fs/ocfs2/aops.c:1901 stack backtrace: CPU: 0 UID: 0 PID: 8063 Comm: syz.2.330 Not tainted 6.11.0-rc7-syzkaller-g5f5673607153 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Call trace: dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:319 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:326 __dump_stack lib/dump_stack.c:93 [inline] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:119 dump_stack+0x1c/0x28 lib/dump_stack.c:128 print_circular_bug+0x150/0x1b8 kernel/locking/lockdep.c:2059 check_noncircular+0x310/0x404 kernel/locking/lockdep.c:2186 check_prev_add kernel/locking/lockdep.c:3133 [inline] check_prevs_add kernel/locking/lockdep.c:3252 [inline] validate_chain kernel/locking/lockdep.c:3868 [inline] __lock_acquire+0x33d8/0x779c kernel/locking/lockdep.c:5142 lock_acquire+0x240/0x728 kernel/locking/lockdep.c:5759 __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:608 __mutex_lock kernel/locking/mutex.c:752 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:804 ocfs2_get_system_file_inode+0x180/0x6d8 fs/ocfs2/sysfile.c:101 ocfs2_reserve_local_alloc_bits+0xe4/0x247c fs/ocfs2/localalloc.c:627 ocfs2_reserve_clusters_with_limit+0x194/0xabc fs/ocfs2/suballoc.c:1166 ocfs2_reserve_clusters fs/ocfs2/suballoc.c:1227 [inline] ocfs2_lock_allocators+0x294/0x584 fs/ocfs2/suballoc.c:2746 ocfs2_write_begin_nolock+0x22cc/0x3e6c fs/ocfs2/aops.c:1739 ocfs2_write_begin+0x1ac/0x38c fs/ocfs2/aops.c:1903 generic_perform_write+0x2e8/0x8e0 mm/filemap.c:4019 __generic_file_write_iter+0xfc/0x204 mm/filemap.c:4121 ocfs2_file_write_iter+0x1520/0x1e10 fs/ocfs2/file.c:2455 new_sync_write fs/read_write.c:497 [inline] vfs_write+0x940/0xc80 fs/read_write.c:590 ksys_write+0x15c/0x26c fs/read_write.c:643 __do_sys_write fs/read_write.c:655 [inline] __se_sys_write fs/read_write.c:652 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:652 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598 OCFS2: ERROR (device loop2): int ocfs2_claim_suballoc_bits(struct ocfs2_alloc_context *, handle_t *, u32, u32, struct ocfs2_suballoc_result *): Chain allocator dinode 23 has 4294967295 used bits but only 16777215 total On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. OCFS2: Returning error to the calling process. (syz.2.330,8063,0):ocfs2_claim_suballoc_bits:2038 ERROR: status = -5 (syz.2.330,8063,0):__ocfs2_claim_clusters:2412 ERROR: status = -5 (syz.2.330,8063,0):__ocfs2_claim_clusters:2420 ERROR: status = -5 (syz.2.330,8063,0):ocfs2_local_alloc_new_window:1197 ERROR: status = -5 (syz.2.330,8063,0):ocfs2_local_alloc_new_window:1222 ERROR: status = -5 (syz.2.330,8063,0):ocfs2_local_alloc_slide_window:1296 ERROR: status = -5 (syz.2.330,8063,0):ocfs2_local_alloc_slide_window:1315 ERROR: status = -5 (syz.2.330,8063,0):ocfs2_reserve_local_alloc_bits:672 ERROR: status = -5 (syz.2.330,8063,0):ocfs2_reserve_local_alloc_bits:710 ERROR: status = -5 (syz.2.330,8063,0):ocfs2_reserve_clusters_with_limit:1170 ERROR: status = -5 (syz.2.330,8063,0):ocfs2_reserve_clusters_with_limit:1219 ERROR: status = -5 (syz.2.330,8063,0):ocfs2_lock_allocators:2749 ERROR: status = -5 (syz.2.330,8063,0):ocfs2_write_begin_nolock:1743 ERROR: status = -5 (syz.2.330,8063,0):ocfs2_write_begin:1906 ERROR: status = -5