====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.1.49/4609 is trying to acquire lock: ffff0000dcd49488 (&osb->system_file_mutex){+.+.}-{3:3}, at: ocfs2_get_system_file_inode+0x158/0x68c fs/ocfs2/sysfile.c:101 but task is already holding lock: ffff0000e137bf60 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_expand_inline_dir fs/ocfs2/dir.c:2819 [inline] ffff0000e137bf60 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_extend_dir+0x4f4/0x3c48 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+0x64/0x300 kernel/locking/rwsem.c:1520 ocfs2_read_virt_blocks+0x23c/0x8c8 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+0x314/0x1d90 fs/ocfs2/dir.c:1091 ocfs2_find_files_on_disk+0x128/0x40c fs/ocfs2/dir.c:1995 ocfs2_lookup_ino_from_name+0x60/0x114 fs/ocfs2/dir.c:2017 _ocfs2_get_system_file_inode fs/ocfs2/sysfile.c:136 [inline] ocfs2_get_system_file_inode+0x2c0/0x68c fs/ocfs2/sysfile.c:112 ocfs2_init_global_system_inodes+0x2b4/0x5c0 fs/ocfs2/super.c:457 ocfs2_initialize_super fs/ocfs2/super.c:2253 [inline] ocfs2_fill_super+0x22ec/0x4198 fs/ocfs2/super.c:994 mount_bdev+0x264/0x35c fs/super.c:1443 ocfs2_mount+0x44/0x58 fs/ocfs2/super.c:1186 legacy_get_tree+0xd8/0x174 fs/fs_context.c:632 vfs_get_tree+0x90/0x278 fs/super.c:1573 do_new_mount+0x228/0x804 fs/namespace.c:3078 path_mount+0x5ac/0xe6c fs/namespace.c:3408 do_mount fs/namespace.c:3421 [inline] __do_sys_mount fs/namespace.c:3629 [inline] __se_sys_mount fs/namespace.c:3606 [inline] __arm64_sys_mount+0x4a0/0x5a0 fs/namespace.c:3606 __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 (&osb->system_file_mutex){+.+.}-{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 __mutex_lock_common+0x1a0/0x1f3c kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799 ocfs2_get_system_file_inode+0x158/0x68c fs/ocfs2/sysfile.c:101 ocfs2_reserve_suballoc_bits+0x100/0x3d40 fs/ocfs2/suballoc.c:798 ocfs2_reserve_new_metadata_blocks+0x340/0x7e4 fs/ocfs2/suballoc.c:1000 ocfs2_expand_inline_dir fs/ocfs2/dir.c:2838 [inline] ocfs2_extend_dir+0x9e8/0x3c48 fs/ocfs2/dir.c:3200 ocfs2_prepare_dir_for_insert+0x2aa8/0x4a80 fs/ocfs2/dir.c:4321 ocfs2_mknod+0x794/0x218c fs/ocfs2/namei.c:294 ocfs2_mkdir+0x19c/0x51c fs/ocfs2/namei.c:657 vfs_mkdir+0x314/0x4d8 fs/namei.c:4114 do_mkdirat+0x1b8/0x3ec fs/namei.c:4139 __do_sys_mkdirat fs/namei.c:4154 [inline] __se_sys_mkdirat fs/namei.c:4152 [inline] __arm64_sys_mkdirat+0x90/0xa8 fs/namei.c:4152 __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: 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.1.49/4609: #0: ffff0000f5698460 (sb_writers#19){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:402 #1: ffff0000e137c2c8 (&type->i_mutex_dir_key#14/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline] #1: ffff0000e137c2c8 (&type->i_mutex_dir_key#14/1){+.+.}-{3:3}, at: filename_create+0x1b0/0x3a8 fs/namei.c:3884 #2: ffff0000e137bf60 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_expand_inline_dir fs/ocfs2/dir.c:2819 [inline] #2: ffff0000e137bf60 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_extend_dir+0x4f4/0x3c48 fs/ocfs2/dir.c:3200 stack backtrace: CPU: 0 PID: 4609 Comm: syz.1.49 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 __mutex_lock_common+0x1a0/0x1f3c kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799 ocfs2_get_system_file_inode+0x158/0x68c fs/ocfs2/sysfile.c:101 ocfs2_reserve_suballoc_bits+0x100/0x3d40 fs/ocfs2/suballoc.c:798 ocfs2_reserve_new_metadata_blocks+0x340/0x7e4 fs/ocfs2/suballoc.c:1000 ocfs2_expand_inline_dir fs/ocfs2/dir.c:2838 [inline] ocfs2_extend_dir+0x9e8/0x3c48 fs/ocfs2/dir.c:3200 ocfs2_prepare_dir_for_insert+0x2aa8/0x4a80 fs/ocfs2/dir.c:4321 ocfs2_mknod+0x794/0x218c fs/ocfs2/namei.c:294 ocfs2_mkdir+0x19c/0x51c fs/ocfs2/namei.c:657 vfs_mkdir+0x314/0x4d8 fs/namei.c:4114 do_mkdirat+0x1b8/0x3ec fs/namei.c:4139 __do_sys_mkdirat fs/namei.c:4154 [inline] __se_sys_mkdirat fs/namei.c:4152 [inline] __arm64_sys_mkdirat+0x90/0xa8 fs/namei.c:4152 __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 OCFS2: ERROR (device loop1): int ocfs2_validate_gd_self(struct super_block *, struct buffer_head *, int): Group descriptor #20 has bad signature On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. OCFS2: File system is now read-only. (syz.1.49,4609,0):ocfs2_search_chain:1783 ERROR: status = -30 (syz.1.49,4609,0):ocfs2_search_chain:1893 ERROR: status = -30 (syz.1.49,4609,0):ocfs2_claim_suballoc_bits:1972 ERROR: status = -30 (syz.1.49,4609,0):ocfs2_claim_suballoc_bits:2015 ERROR: status = -30 (syz.1.49,4609,0):ocfs2_claim_metadata:2040 ERROR: status = -30 (syz.1.49,4609,0):ocfs2_claim_metadata:2053 ERROR: status = -30 (syz.1.49,4609,1):ocfs2_dx_dir_attach_index:2329 ERROR: status = -30 (syz.1.49,4609,1):ocfs2_expand_inline_dir:3022 ERROR: status = -30 (syz.1.49,4609,1):ocfs2_extend_dir:3204 ERROR: status = -30 (syz.1.49,4609,1):ocfs2_prepare_dir_for_insert:4325 ERROR: status = -30 (syz.1.49,4609,1):ocfs2_mknod:298 ERROR: status = -30 (syz.1.49,4609,1):ocfs2_mknod:502 ERROR: status = -30 (syz.1.49,4609,1):ocfs2_mkdir:659 ERROR: status = -30