====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.0.136/4932 is trying to acquire lock: ffff888053f48980 (&type->i_mutex_dir_key#13/3){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline] ffff888053f48980 (&type->i_mutex_dir_key#13/3){+.+.}-{3:3}, at: open_xa_root fs/reiserfs/xattr.c:127 [inline] ffff888053f48980 (&type->i_mutex_dir_key#13/3){+.+.}-{3:3}, at: open_xa_dir+0x11e/0x6f0 fs/reiserfs/xattr.c:152 but task is already holding lock: ffff8880764be090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock_nested+0x5c/0xd0 fs/reiserfs/lock.c:78 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 ( &sbi->lock){+.+.}-{3:3}: __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747 reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27 reiserfs_mkdir+0x30c/0x970 fs/reiserfs/namei.c:831 xattr_mkdir fs/reiserfs/xattr.c:76 [inline] open_xa_root fs/reiserfs/xattr.c:136 [inline] open_xa_dir+0x316/0x6f0 fs/reiserfs/xattr.c:152 xattr_lookup+0x22/0x2a0 fs/reiserfs/xattr.c:395 reiserfs_xattr_set_handle+0xf3/0xca0 fs/reiserfs/xattr.c:533 reiserfs_xattr_set+0x435/0x550 fs/reiserfs/xattr.c:633 __vfs_setxattr+0x3e0/0x420 fs/xattr.c:182 __vfs_setxattr_noperm+0x129/0x5e0 fs/xattr.c:216 vfs_setxattr+0x168/0x2f0 fs/xattr.c:309 do_setxattr fs/xattr.c:594 [inline] setxattr+0x2b2/0x2d0 fs/xattr.c:617 path_setxattr+0x142/0x280 fs/xattr.c:636 __do_sys_lsetxattr fs/xattr.c:659 [inline] __se_sys_lsetxattr fs/xattr.c:655 [inline] __x64_sys_lsetxattr+0xb4/0xd0 fs/xattr.c:655 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #0 (&type->i_mutex_dir_key#13/3){+.+.}-{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+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049 lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662 down_write_nested+0x39/0x60 kernel/locking/rwsem.c:1689 inode_lock_nested include/linux/fs.h:793 [inline] open_xa_root fs/reiserfs/xattr.c:127 [inline] open_xa_dir+0x11e/0x6f0 fs/reiserfs/xattr.c:152 reiserfs_for_each_xattr+0x174/0x7b0 fs/reiserfs/xattr.c:252 reiserfs_delete_xattrs+0x1c/0x80 fs/reiserfs/xattr.c:364 reiserfs_evict_inode+0x221/0x490 fs/reiserfs/inode.c:53 evict+0x485/0x870 fs/inode.c:705 reiserfs_create+0x336/0x680 fs/reiserfs/namei.c:-1 lookup_open fs/namei.c:3482 [inline] open_last_lookups fs/namei.c:3550 [inline] path_openat+0x1187/0x2e70 fs/namei.c:3780 do_filp_open+0x1c1/0x3c0 fs/namei.c:3810 do_sys_openat2+0x142/0x490 fs/open.c:1318 do_sys_open fs/open.c:1334 [inline] __do_sys_openat fs/open.c:1350 [inline] __se_sys_openat fs/open.c:1345 [inline] __x64_sys_openat+0x135/0x160 fs/open.c:1345 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sbi->lock); lock(&type->i_mutex_dir_key#13/3); lock(&sbi->lock); lock(&type->i_mutex_dir_key#13/3); *** DEADLOCK *** 3 locks held by syz.0.136/4932: #0: ffff888070f4a460 (sb_writers#23){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:393 #1: ffff888053f482e0 (&type->i_mutex_dir_key#13){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #1: ffff888053f482e0 (&type->i_mutex_dir_key#13){+.+.}-{3:3}, at: open_last_lookups fs/namei.c:3547 [inline] #1: ffff888053f482e0 (&type->i_mutex_dir_key#13){+.+.}-{3:3}, at: path_openat+0x7c2/0x2e70 fs/namei.c:3780 #2: ffff8880764be090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock_nested+0x5c/0xd0 fs/reiserfs/lock.c:78 stack backtrace: CPU: 0 PID: 4932 Comm: syz.0.136 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 Call Trace: dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106 check_noncircular+0x274/0x310 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+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049 lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662 down_write_nested+0x39/0x60 kernel/locking/rwsem.c:1689 inode_lock_nested include/linux/fs.h:793 [inline] open_xa_root fs/reiserfs/xattr.c:127 [inline] open_xa_dir+0x11e/0x6f0 fs/reiserfs/xattr.c:152 reiserfs_for_each_xattr+0x174/0x7b0 fs/reiserfs/xattr.c:252 reiserfs_delete_xattrs+0x1c/0x80 fs/reiserfs/xattr.c:364 reiserfs_evict_inode+0x221/0x490 fs/reiserfs/inode.c:53 evict+0x485/0x870 fs/inode.c:705 reiserfs_create+0x336/0x680 fs/reiserfs/namei.c:-1 lookup_open fs/namei.c:3482 [inline] open_last_lookups fs/namei.c:3550 [inline] path_openat+0x1187/0x2e70 fs/namei.c:3780 do_filp_open+0x1c1/0x3c0 fs/namei.c:3810 do_sys_openat2+0x142/0x490 fs/open.c:1318 do_sys_open fs/open.c:1334 [inline] __do_sys_openat fs/open.c:1350 [inline] __se_sys_openat fs/open.c:1345 [inline] __x64_sys_openat+0x135/0x160 fs/open.c:1345 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7f438438ebe9 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:00007f4385236038 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 RAX: ffffffffffffffda RBX: 00007f43845b5fa0 RCX: 00007f438438ebe9 RDX: 000000000000275a RSI: 0000200000000040 RDI: ffffffffffffff9c RBP: 00007f4384411e19 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f43845b6038 R14: 00007f43845b5fa0 R15: 00007ffcc57e34b8