REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage. ====================================================== WARNING: possible circular locking dependency detected 6.4.0-rc7-syzkaller-00072-gdad9774deaf1 #0 Not tainted ------------------------------------------------------ syz-executor318/4992 is trying to acquire lock: ffff888077f10980 (&type->i_mutex_dir_key#6/3){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:810 [inline] ffff888077f10980 (&type->i_mutex_dir_key#6/3){+.+.}-{3:3}, at: open_xa_root fs/reiserfs/xattr.c:128 [inline] ffff888077f10980 (&type->i_mutex_dir_key#6/3){+.+.}-{3:3}, at: open_xa_dir+0x136/0x610 fs/reiserfs/xattr.c:153 but task is already holding lock: ffff8880146f1090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock_nested+0x5f/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+0x1e3/0x520 kernel/locking/lockdep.c:5705 __mutex_lock_common+0x1d8/0x2530 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799 reiserfs_write_lock+0x7a/0xd0 fs/reiserfs/lock.c:27 reiserfs_mkdir+0x321/0x8f0 fs/reiserfs/namei.c:829 xattr_mkdir fs/reiserfs/xattr.c:77 [inline] open_xa_root fs/reiserfs/xattr.c:137 [inline] open_xa_dir+0x2cd/0x610 fs/reiserfs/xattr.c:153 xattr_lookup+0x24/0x280 fs/reiserfs/xattr.c:396 reiserfs_xattr_set_handle+0xfc/0xdc0 fs/reiserfs/xattr.c:534 reiserfs_security_write+0x157/0x1d0 fs/reiserfs/xattr_security.c:106 reiserfs_new_inode+0x1631/0x1d40 fs/reiserfs/inode.c:2111 reiserfs_mkdir+0x5b0/0x8f0 fs/reiserfs/namei.c:843 vfs_mkdir+0x29d/0x450 fs/namei.c:4115 do_mkdirat+0x264/0x520 fs/namei.c:4138 __do_sys_mkdir fs/namei.c:4158 [inline] __se_sys_mkdir fs/namei.c:4156 [inline] __x64_sys_mkdir+0x6e/0x80 fs/namei.c:4156 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (&type->i_mutex_dir_key#6/3){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3113 [inline] check_prevs_add kernel/locking/lockdep.c:3232 [inline] validate_chain+0x166b/0x58f0 kernel/locking/lockdep.c:3847 __lock_acquire+0x1316/0x2070 kernel/locking/lockdep.c:5088 lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5705 down_write_nested+0x3d/0x50 kernel/locking/rwsem.c:1689 inode_lock_nested include/linux/fs.h:810 [inline] open_xa_root fs/reiserfs/xattr.c:128 [inline] open_xa_dir+0x136/0x610 fs/reiserfs/xattr.c:153 xattr_lookup+0x24/0x280 fs/reiserfs/xattr.c:396 reiserfs_xattr_get+0xfd/0x570 fs/reiserfs/xattr.c:678 __vfs_getxattr+0x436/0x470 fs/xattr.c:424 smk_fetch+0xb1/0x140 security/smack/smack_lsm.c:295 smack_d_instantiate+0x6d9/0xb40 security/smack/smack_lsm.c:3475 security_d_instantiate+0x9b/0xf0 security/security.c:3760 d_instantiate_new+0x65/0x120 fs/dcache.c:2053 reiserfs_mkdir+0x769/0x8f0 fs/reiserfs/namei.c:877 vfs_mkdir+0x29d/0x450 fs/namei.c:4115 do_mkdirat+0x264/0x520 fs/namei.c:4138 __do_sys_mkdir fs/namei.c:4158 [inline] __se_sys_mkdir fs/namei.c:4156 [inline] __x64_sys_mkdir+0x6e/0x80 fs/namei.c:4156 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sbi->lock); lock(&type->i_mutex_dir_key#6/3); lock(&sbi->lock); lock(&type->i_mutex_dir_key#6/3); *** DEADLOCK *** 3 locks held by syz-executor318/4992: #0: ffff88807c442460 (sb_writers#9){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:394 #1: ffff888077f102e0 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:810 [inline] #1: ffff888077f102e0 (&type->i_mutex_dir_key#6/1){+.+.}-{3:3}, at: filename_create+0x260/0x530 fs/namei.c:3884 #2: ffff8880146f1090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock_nested+0x5f/0xd0 fs/reiserfs/lock.c:78 stack backtrace: CPU: 0 PID: 4992 Comm: syz-executor318 Not tainted 6.4.0-rc7-syzkaller-00072-gdad9774deaf1 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 check_noncircular+0x2fe/0x3b0 kernel/locking/lockdep.c:2188 check_prev_add kernel/locking/lockdep.c:3113 [inline] check_prevs_add kernel/locking/lockdep.c:3232 [inline] validate_chain+0x166b/0x58f0 kernel/locking/lockdep.c:3847 __lock_acquire+0x1316/0x2070 kernel/locking/lockdep.c:5088 lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5705 down_write_nested+0x3d/0x50 kernel/locking/rwsem.c:1689 inode_lock_nested include/linux/fs.h:810 [inline] open_xa_root fs/reiserfs/xattr.c:128 [inline] open_xa_dir+0x136/0x610 fs/reiserfs/xattr.c:153 xattr_lookup+0x24/0x280 fs/reiserfs/xattr.c:396 reiserfs_xattr_get+0xfd/0x570 fs/reiserfs/xattr.c:678 __vfs_getxattr+0x436/0x470 fs/xattr.c:424 smk_fetch+0xb1/0x140 security/smack/smack_lsm.c:295 smack_d_instantiate+0x6d9/0xb40 security/smack/smack_lsm.c:3475 security_d_instantiate+0x9b/0xf0 security/security.c:3760 d_instantiate_new+0x65/0x120 fs/dcache.c:2053 reiserfs_mkdir+0x769/0x8f0 fs/reiserfs/namei.c:877 vfs_mkdir+0x29d/0x450 fs/namei.c:4115 do_mkdirat+0x264/0x520 fs/namei.c:4138 __do_sys_mkdir fs/namei.c:4158 [inline] __se_sys_mkdir fs/namei.c:4156 [inline] __x64_sys_mkdir+0x6e/0x80 fs/namei.c:4156 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f5faf5f4829 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 14 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 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffe048a86c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000053 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f5faf5f4829 RDX: 00007f5faf5b2ea3 RSI: 000000000