loop4: detected capacity change from 0 to 32768 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.2933/19858 is trying to acquire lock: ffff88805cb03f60 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_try_remove_refcount_tree+0xb7/0x340 fs/ocfs2/refcounttree.c:932 but task is already holding lock: ffff88805cb03ff8 (&oi->ip_xattr_sem){++++}-{3:3}, at: ocfs2_try_remove_refcount_tree+0xa5/0x340 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+0x46/0x2e0 kernel/locking/rwsem.c:1520 ocfs2_init_acl+0x30a/0x770 fs/ocfs2/acl.c:366 ocfs2_mknod+0x140f/0x2300 fs/ocfs2/namei.c:410 ocfs2_mkdir+0x196/0x430 fs/ocfs2/namei.c:657 vfs_mkdir+0x296/0x440 fs/namei.c:4121 do_mkdirat+0x1dc/0x450 fs/namei.c:4144 __do_sys_mkdirat fs/namei.c:4159 [inline] __se_sys_mkdirat fs/namei.c:4157 [inline] __x64_sys_mkdirat+0x89/0xa0 fs/namei.c:4157 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #2 (&journal->j_trans_barrier){.+.+}-{3:3}: down_read+0x46/0x2e0 kernel/locking/rwsem.c:1520 ocfs2_start_trans+0x3a8/0x6f0 fs/ocfs2/journal.c:372 ocfs2_mknod+0xf1d/0x2300 fs/ocfs2/namei.c:361 ocfs2_create+0x196/0x430 fs/ocfs2/namei.c:674 lookup_open fs/namei.c:3496 [inline] open_last_lookups fs/namei.c:3564 [inline] path_openat+0x12a0/0x3230 fs/namei.c:3794 do_filp_open+0x1f5/0x430 fs/namei.c:3824 do_sys_openat2+0x134/0x1d0 fs/open.c:1421 do_sys_open fs/open.c:1436 [inline] __do_sys_openat fs/open.c:1452 [inline] __se_sys_openat fs/open.c:1447 [inline] __x64_sys_openat+0x139/0x160 fs/open.c:1447 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #1 (sb_internal#3){.+.+}-{0:0}: percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1633 [inline] sb_start_intwrite include/linux/fs.h:1755 [inline] ocfs2_start_trans+0x2a9/0x6f0 fs/ocfs2/journal.c:370 ocfs2_setattr+0x10b6/0x1bc0 fs/ocfs2/file.c:1250 notify_change+0xb0d/0xe10 fs/attr.c:499 chown_common+0x413/0x5d0 fs/open.c:783 vfs_fchown fs/open.c:851 [inline] ksys_fchown+0xed/0x160 fs/open.c:862 __do_sys_fchown fs/open.c:870 [inline] __se_sys_fchown fs/open.c:868 [inline] __x64_sys_fchown+0x7a/0x90 fs/open.c:868 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #0 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x2df1/0x7d40 kernel/locking/lockdep.c:5137 lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754 down_write+0x97/0x200 kernel/locking/rwsem.c:1573 ocfs2_try_remove_refcount_tree+0xb7/0x340 fs/ocfs2/refcounttree.c:932 ocfs2_truncate_file+0xde5/0x1440 fs/ocfs2/file.c:521 ocfs2_setattr+0x158d/0x1bc0 fs/ocfs2/file.c:1211 notify_change+0xb0d/0xe10 fs/attr.c:499 do_truncate+0x1b0/0x240 fs/open.c:66 do_sys_ftruncate+0x325/0x3d0 fs/open.c:194 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 other info that might help us debug this: Chain exists of: &ocfs2_file_ip_alloc_sem_key --> &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(&ocfs2_file_ip_alloc_sem_key); *** DEADLOCK *** 3 locks held by syz.4.2933/19858: #0: ffff88802609c418 (sb_writers#19){.+.+}-{0:0}, at: do_sys_ftruncate+0x281/0x3d0 fs/open.c:191 #1: ffff88805cb042d8 (&sb->s_type->i_mutex_key#24){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline] #1: ffff88805cb042d8 (&sb->s_type->i_mutex_key#24){+.+.}-{3:3}, at: do_truncate+0x19c/0x240 fs/open.c:64 #2: ffff88805cb03ff8 (&oi->ip_xattr_sem){++++}-{3:3}, at: ocfs2_try_remove_refcount_tree+0xa5/0x340 fs/ocfs2/refcounttree.c:931 stack backtrace: CPU: 0 PID: 19858 Comm: syz.4.2933 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 Call Trace: dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106 check_noncircular+0x2fc/0x400 kernel/locking/lockdep.c:2187 check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x2df1/0x7d40 kernel/locking/lockdep.c:5137 lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754 down_write+0x97/0x200 kernel/locking/rwsem.c:1573 ocfs2_try_remove_refcount_tree+0xb7/0x340 fs/ocfs2/refcounttree.c:932 ocfs2_truncate_file+0xde5/0x1440 fs/ocfs2/file.c:521 ocfs2_setattr+0x158d/0x1bc0 fs/ocfs2/file.c:1211 notify_change+0xb0d/0xe10 fs/attr.c:499 do_truncate+0x1b0/0x240 fs/open.c:66 do_sys_ftruncate+0x325/0x3d0 fs/open.c:194 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7f528d39cdd9 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f528e1ac028 EFLAGS: 00000246 ORIG_RAX: 000000000000004d RAX: ffffffffffffffda RBX: 00007f528d615fa0 RCX: 00007f528d39cdd9 RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000005 RBP: 00007f528d432d69 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f528d616038 R14: 00007f528d615fa0 R15: 00007ffd38595578