====================================================== WARNING: possible circular locking dependency detected 5.15.155-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.1/6736 is trying to acquire lock: ffff88805714e640 (&type->i_mutex_dir_key#16/3){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:824 [inline] ffff88805714e640 (&type->i_mutex_dir_key#16/3){+.+.}-{3:3}, at: open_xa_root fs/reiserfs/xattr.c:127 [inline] ffff88805714e640 (&type->i_mutex_dir_key#16/3){+.+.}-{3:3}, at: open_xa_dir+0x132/0x610 fs/reiserfs/xattr.c:152 but task is already holding lock: ffff888056af5090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock_nested+0x5b/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}: lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 __mutex_lock_common+0x1da/0x25a0 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 reiserfs_write_lock+0x76/0xd0 fs/reiserfs/lock.c:27 reiserfs_mkdir+0x31d/0x8f0 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+0x2c9/0x610 fs/reiserfs/xattr.c:152 xattr_lookup+0x24/0x280 fs/reiserfs/xattr.c:395 reiserfs_xattr_set_handle+0x100/0x10b0 fs/reiserfs/xattr.c:540 __reiserfs_set_acl+0x4fa/0x6a0 fs/reiserfs/xattr_acl.c:276 reiserfs_set_acl+0x4d5/0x6e0 fs/reiserfs/xattr_acl.c:50 set_posix_acl fs/posix_acl.c:947 [inline] posix_acl_xattr_set+0x33b/0x3a0 fs/posix_acl.c:966 __vfs_setxattr+0x3e7/0x420 fs/xattr.c:182 __vfs_setxattr_noperm+0x12a/0x5e0 fs/xattr.c:216 vfs_setxattr+0x21d/0x420 fs/xattr.c:303 do_setxattr fs/xattr.c:588 [inline] setxattr+0x27e/0x2e0 fs/xattr.c:611 path_setxattr+0x1bc/0x2a0 fs/xattr.c:630 __do_sys_lsetxattr fs/xattr.c:653 [inline] __se_sys_lsetxattr fs/xattr.c:649 [inline] __x64_sys_lsetxattr+0xb4/0xd0 fs/xattr.c:649 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #0 (&type->i_mutex_dir_key#16/3){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain+0x1649/0x5930 kernel/locking/lockdep.c:3788 __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5012 lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 down_write_nested+0x3b/0x60 kernel/locking/rwsem.c:1667 inode_lock_nested include/linux/fs.h:824 [inline] open_xa_root fs/reiserfs/xattr.c:127 [inline] open_xa_dir+0x132/0x610 fs/reiserfs/xattr.c:152 reiserfs_for_each_xattr+0x1a4/0xb40 fs/reiserfs/xattr.c:252 reiserfs_delete_xattrs+0x1b/0x80 fs/reiserfs/xattr.c:364 reiserfs_evict_inode+0x20c/0x460 fs/reiserfs/inode.c:53 evict+0x2a4/0x620 fs/inode.c:587 reiserfs_new_inode+0x7bd/0x1d90 fs/reiserfs/inode.c:2164 reiserfs_mkdir+0x5ac/0x8f0 fs/reiserfs/namei.c:845 vfs_mkdir+0x3b6/0x590 fs/namei.c:4065 do_mkdirat+0x260/0x520 fs/namei.c:4090 __do_sys_mkdir fs/namei.c:4110 [inline] __se_sys_mkdir fs/namei.c:4108 [inline] __x64_sys_mkdir+0x6a/0x80 fs/namei.c:4108 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sbi->lock); lock(&type->i_mutex_dir_key#16/3); lock(&sbi->lock); lock(&type->i_mutex_dir_key#16/3); *** DEADLOCK *** 3 locks held by syz-executor.1/6736: #0: ffff888073f9a460 (sb_writers#20){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:377 #1: ffff88805714dfa0 (&type->i_mutex_dir_key#16/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:824 [inline] #1: ffff88805714dfa0 (&type->i_mutex_dir_key#16/1){+.+.}-{3:3}, at: filename_create+0x25c/0x530 fs/namei.c:3835 #2: ffff888056af5090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock_nested+0x5b/0xd0 fs/reiserfs/lock.c:78 stack backtrace: CPU: 1 PID: 6736 Comm: syz-executor.1 Not tainted 5.15.155-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106 check_noncircular+0x2f8/0x3b0 kernel/locking/lockdep.c:2133 check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain+0x1649/0x5930 kernel/locking/lockdep.c:3788 __lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5012 lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623 down_write_nested+0x3b/0x60 kernel/locking/rwsem.c:1667 inode_lock_nested include/linux/fs.h:824 [inline] open_xa_root fs/reiserfs/xattr.c:127 [inline] open_xa_dir+0x132/0x610 fs/reiserfs/xattr.c:152 reiserfs_for_each_xattr+0x1a4/0xb40 fs/reiserfs/xattr.c:252 reiserfs_delete_xattrs+0x1b/0x80 fs/reiserfs/xattr.c:364 reiserfs_evict_inode+0x20c/0x460 fs/reiserfs/inode.c:53 evict+0x2a4/0x620 fs/inode.c:587 reiserfs_new_inode+0x7bd/0x1d90 fs/reiserfs/inode.c:2164 reiserfs_mkdir+0x5ac/0x8f0 fs/reiserfs/namei.c:845 vfs_mkdir+0x3b6/0x590 fs/namei.c:4065 do_mkdirat+0x260/0x520 fs/namei.c:4090 __do_sys_mkdir fs/namei.c:4110 [inline] __se_sys_mkdir fs/namei.c:4108 [inline] __x64_sys_mkdir+0x6a/0x80 fs/namei.c:4108 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 RIP: 0033:0x7f6414bc2e69 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f64131140c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000053 RAX: ffffffffffffffda RBX: 00007f6414cf1050 RCX: 00007f6414bc2e69 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000200002c0 RBP: 00007f6414c0f47a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000006e R14: 00007f6414cf1050 R15: 00007fffb31c8de8