JBD2: Ignoring recovery information on journal jbd2_journal_bmap: journal block not found at offset 32 on loop2-75 JBD2: bad block at offset 32 ocfs2: Mounting device (7,2) on (node local, slot 0) with ordered data mode. ====================================================== WARNING: possible circular locking dependency detected 6.1.138-syzkaller #0 Not tainted ------------------------------------------------------ syz.2.397/6413 is trying to acquire lock: ffff888018ab9488 (&osb->system_file_mutex){+.+.}-{3:3}, at: ocfs2_get_system_file_inode+0x1a2/0x7b0 fs/ocfs2/sysfile.c:101 but task is already holding lock: ffff888050f1b120 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_expand_inline_dir fs/ocfs2/dir.c:2819 [inline] ffff888050f1b120 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_extend_dir+0x662/0x48d0 fs/ocfs2/dir.c:3200 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+0x42/0x2d0 kernel/locking/rwsem.c:1520 ocfs2_read_virt_blocks+0x265/0x950 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+0x3d1/0x20c0 fs/ocfs2/dir.c:1091 ocfs2_find_files_on_disk+0x102/0x390 fs/ocfs2/dir.c:1995 ocfs2_lookup_ino_from_name+0x4f/0xf0 fs/ocfs2/dir.c:2017 _ocfs2_get_system_file_inode fs/ocfs2/sysfile.c:136 [inline] ocfs2_get_system_file_inode+0x332/0x7b0 fs/ocfs2/sysfile.c:112 ocfs2_init_global_system_inodes+0x316/0x650 fs/ocfs2/super.c:457 ocfs2_initialize_super fs/ocfs2/super.c:2250 [inline] ocfs2_fill_super+0x2a32/0x4d00 fs/ocfs2/super.c:994 mount_bdev+0x287/0x3c0 fs/super.c:1443 legacy_get_tree+0xe6/0x180 fs/fs_context.c:632 vfs_get_tree+0x88/0x270 fs/super.c:1573 do_new_mount+0x24a/0xa40 fs/namespace.c:3057 do_mount fs/namespace.c:3400 [inline] __do_sys_mount fs/namespace.c:3608 [inline] __se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3585 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #0 (&osb->system_file_mutex){+.+.}-{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+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049 lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747 ocfs2_get_system_file_inode+0x1a2/0x7b0 fs/ocfs2/sysfile.c:101 ocfs2_reserve_suballoc_bits+0x135/0x4630 fs/ocfs2/suballoc.c:776 ocfs2_reserve_new_metadata_blocks+0x400/0x940 fs/ocfs2/suballoc.c:978 ocfs2_expand_inline_dir fs/ocfs2/dir.c:2838 [inline] ocfs2_extend_dir+0xc70/0x48d0 fs/ocfs2/dir.c:3200 ocfs2_prepare_dir_for_insert+0x30ae/0x53e0 fs/ocfs2/dir.c:4321 ocfs2_mknod+0x876/0x2350 fs/ocfs2/namei.c:294 ocfs2_create+0x1b6/0x4a0 fs/ocfs2/namei.c:674 lookup_open fs/namei.c:3482 [inline] open_last_lookups fs/namei.c:3550 [inline] path_openat+0x1187/0x2e70 fs/namei.c:3780 do_filp_open+0x1c1/0x3c0 fs/namei.c:3810 do_sys_openat2+0x142/0x490 fs/open.c:1318 do_sys_open fs/open.c:1334 [inline] __do_sys_creat fs/open.c:1412 [inline] __se_sys_creat fs/open.c:1406 [inline] __x64_sys_creat+0x8c/0xb0 fs/open.c:1406 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 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 *** 3 locks held by syz.2.397/6413: #0: ffff88807ce42460 (sb_writers#29){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:393 #1: ffff888050f1b488 (&type->i_mutex_dir_key#19){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #1: ffff888050f1b488 (&type->i_mutex_dir_key#19){++++}-{3:3}, at: open_last_lookups fs/namei.c:3547 [inline] #1: ffff888050f1b488 (&type->i_mutex_dir_key#19){++++}-{3:3}, at: path_openat+0x7c2/0x2e70 fs/namei.c:3780 #2: ffff888050f1b120 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_expand_inline_dir fs/ocfs2/dir.c:2819 [inline] #2: ffff888050f1b120 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_extend_dir+0x662/0x48d0 fs/ocfs2/dir.c:3200 stack backtrace: CPU: 0 PID: 6413 Comm: syz.2.397 Not tainted 6.1.138-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025 Call Trace: dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106 check_noncircular+0x274/0x310 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+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049 lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747 ocfs2_get_system_file_inode+0x1a2/0x7b0 fs/ocfs2/sysfile.c:101 ocfs2_reserve_suballoc_bits+0x135/0x4630 fs/ocfs2/suballoc.c:776 ocfs2_reserve_new_metadata_blocks+0x400/0x940 fs/ocfs2/suballoc.c:978 ocfs2_expand_inline_dir fs/ocfs2/dir.c:2838 [inline] ocfs2_extend_dir+0xc70/0x48d0 fs/ocfs2/dir.c:3200 ocfs2_prepare_dir_for_insert+0x30ae/0x53e0 fs/ocfs2/dir.c:4321 ocfs2_mknod+0x876/0x2350 fs/ocfs2/namei.c:294 ocfs2_create+0x1b6/0x4a0 fs/ocfs2/namei.c:674 lookup_open fs/namei.c:3482 [inline] open_last_lookups fs/namei.c:3550 [inline] path_openat+0x1187/0x2e70 fs/namei.c:3780 do_filp_open+0x1c1/0x3c0 fs/namei.c:3810 do_sys_openat2+0x142/0x490 fs/open.c:1318 do_sys_open fs/open.c:1334 [inline] __do_sys_creat fs/open.c:1412 [inline] __se_sys_creat fs/open.c:1406 [inline] __x64_sys_creat+0x8c/0xb0 fs/open.c:1406 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7fb82218e969 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fb82303f038 EFLAGS: 00000246 ORIG_RAX: 0000000000000055 RAX: ffffffffffffffda RBX: 00007fb8223b5fa0 RCX: 00007fb82218e969 RDX: 0000000000000000 RSI: 00000000000000ec RDI: 0000200000000e00 RBP: 00007fb822210ab1 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007fb8223b5fa0 R15: 00007fff98e16bc8 OCFS2: ERROR (device loop2): int ocfs2_claim_suballoc_bits(struct ocfs2_alloc_context *, handle_t *, u32, u32, struct ocfs2_suballoc_result *): Chain allocator dinode 73 has 4294901761 used bits but only 0 total On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. OCFS2: File system is now read-only. (syz.2.397,6413,0):ocfs2_claim_suballoc_bits:1983 ERROR: status = -30 (syz.2.397,6413,0):ocfs2_claim_metadata:2008 ERROR: status = -30 (syz.2.397,6413,0):ocfs2_claim_metadata:2021 ERROR: status = -30 (syz.2.397,6413,0):ocfs2_dx_dir_attach_index:2329 ERROR: status = -30 (syz.2.397,6413,0):ocfs2_expand_inline_dir:3022 ERROR: status = -30 (syz.2.397,6413,0):ocfs2_extend_dir:3204 ERROR: status = -30 (syz.2.397,6413,0):ocfs2_prepare_dir_for_insert:4325 ERROR: status = -30 (syz.2.397,6413,0):ocfs2_mknod:298 ERROR: status = -30 (syz.2.397,6413,0):ocfs2_mknod:502 ERROR: status = -30 (syz.2.397,6413,0):ocfs2_create:676 ERROR: status = -30 syz.2.397 (6413) used greatest stack depth: 18368 bytes left