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 6.6.102-syzkaller #0 Not tainted ------------------------------------------------------ syz.1.404/7936 is trying to acquire lock: ffff88805f15c2d8 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#6){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline] ffff88805f15c2d8 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#6){+.+.}-{3:3}, at: ocfs2_xattr_set+0xada/0x11f0 fs/ocfs2/xattr.c:3622 but task is already holding lock: ffff88805f15b1b8 (&oi->ip_xattr_sem){++++}-{3:3}, at: ocfs2_xattr_set+0x410/0x11f0 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){++++}-{3:3}: down_read+0x46/0x2e0 kernel/locking/rwsem.c:1520 ocfs2_init_acl+0x2fa/0x720 fs/ocfs2/acl.c:366 ocfs2_mknod+0x12e5/0x20f0 fs/ocfs2/namei.c:410 ocfs2_create+0x196/0x410 fs/ocfs2/namei.c:674 lookup_open fs/namei.c:3488 [inline] open_last_lookups fs/namei.c:3556 [inline] path_openat+0x1277/0x3190 fs/namei.c:3786 do_filp_open+0x1c5/0x3d0 fs/namei.c:3816 do_sys_openat2+0x12c/0x1c0 fs/open.c:1419 do_sys_open fs/open.c:1434 [inline] __do_sys_openat fs/open.c:1450 [inline] __se_sys_openat fs/open.c:1445 [inline] __x64_sys_openat+0x139/0x160 fs/open.c:1445 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #1 (jbd2_handle){++++}-{0:0}: jbd2_journal_lock_updates+0xab/0x380 fs/jbd2/transaction.c:865 __ocfs2_flush_truncate_log+0x2b8/0x10b0 fs/ocfs2/alloc.c:6030 ocfs2_flush_truncate_log+0x4f/0x60 fs/ocfs2/alloc.c:6077 ocfs2_sync_fs+0x117/0x310 fs/ocfs2/super.c:402 sync_filesystem+0x1c2/0x220 fs/sync.c:66 ocfs2_remount+0xf6/0xa50 fs/ocfs2/super.c:611 reconfigure_super+0x21e/0x880 fs/super.c:1151 vfs_cmd_reconfigure fs/fsopen.c:267 [inline] vfs_fsconfig_locked+0x16c/0x320 fs/fsopen.c:296 __do_sys_fsconfig fs/fsopen.c:475 [inline] __se_sys_fsconfig+0x700/0x850 fs/fsopen.c:349 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #0 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#6){+.+.}-{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+0x2ddb/0x7c80 kernel/locking/lockdep.c:5137 lock_acquire+0x197/0x410 kernel/locking/lockdep.c:5754 down_write+0x97/0x1f0 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:804 [inline] ocfs2_xattr_set+0xada/0x11f0 fs/ocfs2/xattr.c:3622 __vfs_setxattr+0x431/0x470 fs/xattr.c:201 __vfs_setxattr_noperm+0x12d/0x5e0 fs/xattr.c:235 vfs_setxattr+0x16c/0x2f0 fs/xattr.c:322 do_setxattr fs/xattr.c:630 [inline] __do_sys_fsetxattr fs/xattr.c:711 [inline] __se_sys_fsetxattr+0x426/0x4b0 fs/xattr.c:687 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 other info that might help us debug this: Chain exists of: &ocfs2_sysfile_lock_key[args->fi_sysfile_type]#6 --> 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]#6); *** DEADLOCK *** 3 locks held by syz.1.404/7936: #0: ffff888054632418 (sb_writers#16){.+.+}-{0:0}, at: mnt_want_write_file+0x63/0x200 fs/namespace.c:447 #1: ffff88805f15b498 (&sb->s_type->i_mutex_key#23){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline] #1: ffff88805f15b498 (&sb->s_type->i_mutex_key#23){+.+.}-{3:3}, at: vfs_setxattr+0x145/0x2f0 fs/xattr.c:321 #2: ffff88805f15b1b8 (&oi->ip_xattr_sem){++++}-{3:3}, at: ocfs2_xattr_set+0x410/0x11f0 fs/ocfs2/xattr.c:3583 stack backtrace: CPU: 1 PID: 7936 Comm: syz.1.404 Not tainted 6.6.102-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 Call Trace: dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106 check_noncircular+0x2bd/0x3c0 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+0x2ddb/0x7c80 kernel/locking/lockdep.c:5137 lock_acquire+0x197/0x410 kernel/locking/lockdep.c:5754 down_write+0x97/0x1f0 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:804 [inline] ocfs2_xattr_set+0xada/0x11f0 fs/ocfs2/xattr.c:3622 __vfs_setxattr+0x431/0x470 fs/xattr.c:201 __vfs_setxattr_noperm+0x12d/0x5e0 fs/xattr.c:235 vfs_setxattr+0x16c/0x2f0 fs/xattr.c:322 do_setxattr fs/xattr.c:630 [inline] __do_sys_fsetxattr fs/xattr.c:711 [inline] __se_sys_fsetxattr+0x426/0x4b0 fs/xattr.c:687 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7f061538ebe9 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:00007f0616208038 EFLAGS: 00000246 ORIG_RAX: 00000000000000be RAX: ffffffffffffffda RBX: 00007f06155b5fa0 RCX: 00007f061538ebe9 RDX: 00002000000000c0 RSI: 0000200000000040 RDI: 0000000000000004 RBP: 00007f0615411e19 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000014 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f06155b6038 R14: 00007f06155b5fa0 R15: 00007ffd2a9fdc28