JBD2: Ignoring recovery information on journal ocfs2: Mounting device (7,1) on (node local, slot 0) with ordered data mode. ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.1.79/4809 is trying to acquire lock: ffff0000e217bf60 (&oi->ip_alloc_sem){++++}-{3:3}, at: ocfs2_try_remove_refcount_tree+0xb4/0x2e4 fs/ocfs2/refcounttree.c:932 but task is already holding lock: ffff0000e217bff8 (&oi->ip_xattr_sem){++++}-{3:3}, at: ocfs2_try_remove_refcount_tree+0xa8/0x2e4 fs/ocfs2/refcounttree.c:931 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&oi->ip_xattr_sem){++++}-{3:3}: down_read+0x64/0x300 kernel/locking/rwsem.c:1520 ocfs2_init_acl+0x264/0x61c fs/ocfs2/acl.c:365 ocfs2_mknod+0x12b0/0x218c fs/ocfs2/namei.c:410 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 -> #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#4){.+.+}-{0:0}: __lock_release kernel/locking/lockdep.c:5376 [inline] lock_release+0x308/0x90c kernel/locking/lockdep.c:5682 up_write+0x48/0x5c0 kernel/locking/rwsem.c:1625 inode_unlock include/linux/fs.h:763 [inline] ocfs2_free_ac_resource fs/ocfs2/suballoc.c:126 [inline] ocfs2_free_alloc_context+0x94/0x18c fs/ocfs2/suballoc.c:140 ocfs2_write_begin_nolock+0x39ec/0x3a80 fs/ocfs2/aops.c:1827 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 (&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+0x27c8/0x6610 kernel/locking/lockdep.c:5049 lock_acquire+0x20c/0x638 kernel/locking/lockdep.c:5662 down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 ocfs2_try_remove_refcount_tree+0xb4/0x2e4 fs/ocfs2/refcounttree.c:932 ocfs2_xattr_set+0x484/0xf0c fs/ocfs2/xattr.c:3673 ocfs2_set_acl+0x410/0x4cc fs/ocfs2/acl.c:254 ocfs2_iop_set_acl+0x178/0x258 fs/ocfs2/acl.c:285 set_posix_acl fs/posix_acl.c:1160 [inline] posix_acl_xattr_set+0x2f8/0x394 fs/posix_acl.c:1189 __vfs_removexattr+0x364/0x380 fs/xattr.c:479 __vfs_removexattr_locked+0x1d0/0x208 fs/xattr.c:514 vfs_removexattr+0x80/0x18c fs/xattr.c:536 ovl_do_removexattr fs/overlayfs/overlayfs.h:270 [inline] ovl_workdir_create+0x358/0x66c fs/overlayfs/super.c:821 ovl_make_workdir fs/overlayfs/super.c:1389 [inline] ovl_get_workdir+0x31c/0x1084 fs/overlayfs/super.c:1539 ovl_fill_super+0x17d0/0x3938 fs/overlayfs/super.c:2095 mount_nodev+0x68/0x108 fs/super.c:1489 ovl_mount+0x3c/0x50 fs/overlayfs/super.c:2186 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 other info that might help us debug this: Chain exists of: &oi->ip_alloc_sem --> &journal->j_trans_barrier --> &oi->ip_xattr_sem Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&oi->ip_xattr_sem); lock(&journal->j_trans_barrier); lock(&oi->ip_xattr_sem); lock(&oi->ip_alloc_sem); *** DEADLOCK *** 5 locks held by syz.1.79/4809: #0: ffff0000f51d80e0 (&type->s_umount_key#68/1){+.+.}-{3:3}, at: alloc_super+0x1a0/0x840 fs/super.c:228 #1: ffff0000db55e460 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:402 #2: ffff0000e217a648 (&sb->s_type->i_mutex_key#26/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline] #2: ffff0000e217a648 (&sb->s_type->i_mutex_key#26/1){+.+.}-{3:3}, at: ovl_workdir_create+0x128/0x66c fs/overlayfs/super.c:771 #3: ffff0000e217c2c8 (&sb->s_type->i_mutex_key#26){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #3: ffff0000e217c2c8 (&sb->s_type->i_mutex_key#26){+.+.}-{3:3}, at: vfs_removexattr+0x6c/0x18c fs/xattr.c:535 #4: ffff0000e217bff8 (&oi->ip_xattr_sem){++++}-{3:3}, at: ocfs2_try_remove_refcount_tree+0xa8/0x2e4 fs/ocfs2/refcounttree.c:931 stack backtrace: CPU: 0 PID: 4809 Comm: syz.1.79 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/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:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x27c8/0x6610 kernel/locking/lockdep.c:5049 lock_acquire+0x20c/0x638 kernel/locking/lockdep.c:5662 down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 ocfs2_try_remove_refcount_tree+0xb4/0x2e4 fs/ocfs2/refcounttree.c:932 ocfs2_xattr_set+0x484/0xf0c fs/ocfs2/xattr.c:3673 ocfs2_set_acl+0x410/0x4cc fs/ocfs2/acl.c:254 ocfs2_iop_set_acl+0x178/0x258 fs/ocfs2/acl.c:285 set_posix_acl fs/posix_acl.c:1160 [inline] posix_acl_xattr_set+0x2f8/0x394 fs/posix_acl.c:1189 __vfs_removexattr+0x364/0x380 fs/xattr.c:479 __vfs_removexattr_locked+0x1d0/0x208 fs/xattr.c:514 vfs_removexattr+0x80/0x18c fs/xattr.c:536 ovl_do_removexattr fs/overlayfs/overlayfs.h:270 [inline] ovl_workdir_create+0x358/0x66c fs/overlayfs/super.c:821 ovl_make_workdir fs/overlayfs/super.c:1389 [inline] ovl_get_workdir+0x31c/0x1084 fs/overlayfs/super.c:1539 ovl_fill_super+0x17d0/0x3938 fs/overlayfs/super.c:2095 mount_nodev+0x68/0x108 fs/super.c:1489 ovl_mount+0x3c/0x50 fs/overlayfs/super.c:2186 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 overlayfs: upper fs does not support tmpfile. overlayfs: upper fs does not support RENAME_WHITEOUT. OCFS2: ERROR (device loop1): 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: File system is now read-only. (syz.1.79,4809,1):ocfs2_claim_suballoc_bits:1993 ERROR: status = -30 (syz.1.79,4809,1):__ocfs2_claim_clusters:2365 ERROR: status = -30 (syz.1.79,4809,1):__ocfs2_claim_clusters:2373 ERROR: status = -30 (syz.1.79,4809,1):ocfs2_block_group_alloc_contig:433 ERROR: status = -30 (syz.1.79,4809,1):ocfs2_block_group_alloc:705 ERROR: status = -30 (syz.1.79,4809,1):ocfs2_block_group_alloc:758 ERROR: status = -30 (syz.1.79,4809,1):ocfs2_reserve_suballoc_bits:833 ERROR: status = -30 (syz.1.79,4809,1):ocfs2_reserve_suballoc_bits:850 ERROR: status = -30 (syz.1.79,4809,1):ocfs2_reserve_new_metadata_blocks:990 ERROR: status = -30 (syz.1.79,4809,1):ocfs2_reserve_new_metadata_blocks:1013 ERROR: status = -30 (syz.1.79,4809,1):ocfs2_init_xattr_set_ctxt:3284 ERROR: status = -30 (syz.1.79,4809,1):ocfs2_xattr_set:3641 ERROR: status = -30 overlayfs: failed to set xattr on upper overlayfs: ...falling back to index=off,metacopy=off. overlayfs: upper fs missing required features.