JBD2: Ignoring recovery information on journal ocfs2: Mounting device (7,5) on (node local, slot 0) with ordered data mode. ====================================================== WARNING: possible circular locking dependency detected 6.16.0-rc4-syzkaller-00013-g66701750d556 #0 Not tainted ------------------------------------------------------ syz.5.878/9104 is trying to acquire lock: ffff88807772c2c0 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#8){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:869 [inline] ffff88807772c2c0 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#8){+.+.}-{4:4}, at: ocfs2_xattr_set+0xd35/0x2a80 fs/ocfs2/xattr.c:3622 but task is already holding lock: ffff888053ef4e38 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_xattr_set+0x429/0x2a80 fs/ocfs2/xattr.c:3583 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&oi->ip_xattr_sem){++++}-{4:4}: down_read+0x9b/0x480 kernel/locking/rwsem.c:1524 ocfs2_init_acl+0x2fc/0x7d0 fs/ocfs2/acl.c:366 ocfs2_mknod+0xd5c/0x2540 fs/ocfs2/namei.c:410 ocfs2_create+0x17c/0x460 fs/ocfs2/namei.c:673 vfs_create fs/namei.c:3414 [inline] vfs_create+0x4e0/0x7a0 fs/namei.c:3398 do_mknodat+0x3d3/0x5d0 fs/namei.c:4294 __do_sys_mknod fs/namei.c:4327 [inline] __se_sys_mknod fs/namei.c:4325 [inline] __x64_sys_mknod+0x87/0xb0 fs/namei.c:4325 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #1 (jbd2_handle){++++}-{0:0}: jbd2_journal_lock_updates+0xa4/0x380 fs/jbd2/transaction.c:861 __ocfs2_flush_truncate_log+0x281/0x1160 fs/ocfs2/alloc.c:6037 ocfs2_flush_truncate_log+0x4a/0x70 fs/ocfs2/alloc.c:6084 ocfs2_sync_fs+0x1c6/0x3d0 fs/ocfs2/super.c:406 sync_filesystem+0x1d0/0x290 fs/sync.c:66 generic_shutdown_super+0x74/0x390 fs/super.c:622 kill_block_super+0x3b/0x90 fs/super.c:1755 deactivate_locked_super+0xc1/0x1a0 fs/super.c:474 deactivate_super fs/super.c:507 [inline] deactivate_super+0xde/0x100 fs/super.c:503 cleanup_mnt+0x225/0x450 fs/namespace.c:1417 task_work_run+0x150/0x240 kernel/task_work.c:227 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] exit_to_user_mode_loop+0xeb/0x110 kernel/entry/common.c:114 exit_to_user_mode_prepare include/linux/entry-common.h:330 [inline] syscall_exit_to_user_mode_work include/linux/entry-common.h:414 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:449 [inline] do_syscall_64+0x3f6/0x4c0 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#8){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3168 [inline] check_prevs_add kernel/locking/lockdep.c:3287 [inline] validate_chain kernel/locking/lockdep.c:3911 [inline] __lock_acquire+0x126f/0x1c90 kernel/locking/lockdep.c:5240 lock_acquire kernel/locking/lockdep.c:5871 [inline] lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5828 down_write+0x92/0x200 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:869 [inline] ocfs2_xattr_set+0xd35/0x2a80 fs/ocfs2/xattr.c:3622 __vfs_setxattr+0x175/0x1e0 fs/xattr.c:200 __vfs_setxattr_noperm+0x127/0x660 fs/xattr.c:234 __vfs_setxattr_locked+0x182/0x260 fs/xattr.c:295 vfs_setxattr+0x145/0x360 fs/xattr.c:321 do_setxattr+0x145/0x180 fs/xattr.c:636 filename_setxattr+0x16b/0x1d0 fs/xattr.c:665 path_setxattrat+0x1de/0x2a0 fs/xattr.c:713 __do_sys_setxattr fs/xattr.c:747 [inline] __se_sys_setxattr fs/xattr.c:743 [inline] __x64_sys_setxattr+0xc6/0x140 fs/xattr.c:743 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f other info that might help us debug this: Chain exists of: &ocfs2_sysfile_lock_key[args->fi_sysfile_type]#8 --> jbd2_handle --> &oi->ip_xattr_sem Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&oi->ip_xattr_sem); lock(jbd2_handle); lock(&oi->ip_xattr_sem); lock(&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#8); *** DEADLOCK *** 3 locks held by syz.5.878/9104: #0: ffff88805a3f2428 (sb_writers#23){.+.+}-{0:0}, at: filename_setxattr+0xbb/0x1d0 fs/xattr.c:663 #1: ffff888053ef5100 (&sb->s_type->i_mutex_key#34){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:869 [inline] #1: ffff888053ef5100 (&sb->s_type->i_mutex_key#34){+.+.}-{4:4}, at: vfs_setxattr+0x122/0x360 fs/xattr.c:320 #2: ffff888053ef4e38 (&oi->ip_xattr_sem){++++}-{4:4}, at: ocfs2_xattr_set+0x429/0x2a80 fs/ocfs2/xattr.c:3583 stack backtrace: CPU: 0 UID: 0 PID: 9104 Comm: syz.5.878 Not tainted 6.16.0-rc4-syzkaller-00013-g66701750d556 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_circular_bug+0x275/0x350 kernel/locking/lockdep.c:2046 check_noncircular+0x14c/0x170 kernel/locking/lockdep.c:2178 check_prev_add kernel/locking/lockdep.c:3168 [inline] check_prevs_add kernel/locking/lockdep.c:3287 [inline] validate_chain kernel/locking/lockdep.c:3911 [inline] __lock_acquire+0x126f/0x1c90 kernel/locking/lockdep.c:5240 lock_acquire kernel/locking/lockdep.c:5871 [inline] lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5828 down_write+0x92/0x200 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:869 [inline] ocfs2_xattr_set+0xd35/0x2a80 fs/ocfs2/xattr.c:3622 __vfs_setxattr+0x175/0x1e0 fs/xattr.c:200 __vfs_setxattr_noperm+0x127/0x660 fs/xattr.c:234 __vfs_setxattr_locked+0x182/0x260 fs/xattr.c:295 vfs_setxattr+0x145/0x360 fs/xattr.c:321 do_setxattr+0x145/0x180 fs/xattr.c:636 filename_setxattr+0x16b/0x1d0 fs/xattr.c:665 path_setxattrat+0x1de/0x2a0 fs/xattr.c:713 __do_sys_setxattr fs/xattr.c:747 [inline] __se_sys_setxattr fs/xattr.c:743 [inline] __x64_sys_setxattr+0xc6/0x140 fs/xattr.c:743 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f472b58e929 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:00007f472c4b1038 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc RAX: ffffffffffffffda RBX: 00007f472b7b5fa0 RCX: 00007f472b58e929 RDX: 0000200000000180 RSI: 00002000000000c0 RDI: 0000200000000040 RBP: 00007f472b610b39 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000020 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f472b7b5fa0 R15: 00007ffd368f1cc8