======================================================
WARNING: possible circular locking dependency detected
6.5.0-rc1-syzkaller-00006-g3f01e9fed845 #0 Not tainted
------------------------------------------------------
syz-executor.1/9203 is trying to acquire lock:
ffff88803d0f2400 (&type->i_mutex_dir_key#12/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:806 [inline]
ffff88803d0f2400 (&type->i_mutex_dir_key#12/1){+.+.}-{3:3}, at: filename_create+0x260/0x530 fs/namei.c:3886

but task is already holding lock:
ffff8880136a8410 (sb_writers#20){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:403

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (sb_writers#20){.+.+}-{0:0}:
       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
       __sb_start_write include/linux/fs.h:1494 [inline]
       sb_start_write+0x4d/0x1c0 include/linux/fs.h:1569
       mnt_want_write_file+0x61/0x200 fs/namespace.c:447
       reiserfs_ioctl+0x177/0x350 fs/reiserfs/ioctl.c:103
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:870 [inline]
       __se_sys_ioctl+0xf8/0x170 fs/ioctl.c:856
       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

-> #1 (&sbi->lock){+.+.}-{3:3}:
       __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_lookup+0x162/0x580 fs/reiserfs/namei.c:364
       lookup_one_qstr_excl+0x11b/0x250 fs/namei.c:1605
       filename_create+0x297/0x530 fs/namei.c:3887
       do_mknodat+0x1ac/0x6e0 fs/namei.c:4032
       __do_sys_mknodat fs/namei.c:4073 [inline]
       __se_sys_mknodat fs/namei.c:4070 [inline]
       __x64_sys_mknodat+0xa9/0xc0 fs/namei.c:4070
       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#12/1){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3142 [inline]
       check_prevs_add kernel/locking/lockdep.c:3261 [inline]
       validate_chain kernel/locking/lockdep.c:3876 [inline]
       __lock_acquire+0x39ff/0x7f70 kernel/locking/lockdep.c:5144
       lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5761
       down_write_nested+0x3d/0x50 kernel/locking/rwsem.c:1689
       inode_lock_nested include/linux/fs.h:806 [inline]
       filename_create+0x260/0x530 fs/namei.c:3886
       do_mkdirat+0xb7/0x520 fs/namei.c:4132
       __do_sys_mkdirat fs/namei.c:4155 [inline]
       __se_sys_mkdirat fs/namei.c:4153 [inline]
       __x64_sys_mkdirat+0x89/0xa0 fs/namei.c:4153
       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:

Chain exists of:
  &type->i_mutex_dir_key#12/1 --> &sbi->lock --> sb_writers#20

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  rlock(sb_writers#20);
                               lock(&sbi->lock);
                               lock(sb_writers#20);
  lock(&type->i_mutex_dir_key
#12
/1);

 *** DEADLOCK ***

1 lock held by syz-executor.1/9203:
 #0: ffff8880136a8410 (
sb_writers#20){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:403

stack backtrace:
CPU: 0 PID: 9203 Comm: syz-executor.1 Not tainted 6.5.0-rc1-syzkaller-00006-g3f01e9fed845 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
 check_noncircular+0x375/0x4a0 kernel/locking/lockdep.c:2195
 check_prev_add kernel/locking/lockdep.c:3142 [inline]
 check_prevs_add kernel/locking/lockdep.c:3261 [inline]
 validate_chain kernel/locking/lockdep.c:3876 [inline]
 __lock_acquire+0x39ff/0x7f70 kernel/locking/lockdep.c:5144
 lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5761
 down_write_nested+0x3d/0x50 kernel/locking/rwsem.c:1689
 inode_lock_nested include/linux/fs.h:806 [inline]
 filename_create+0x260/0x530 fs/namei.c:3886
 do_mkdirat+0xb7/0x520 fs/namei.c:4132
 __do_sys_mkdirat fs/namei.c:4155 [inline]
 __se_sys_mkdirat fs/namei.c:4153 [inline]
 __x64_sys_mkdirat+0x89/0xa0 fs/namei.c:4153
 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:0x7f481d28c389
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f481df7d168 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007f481d3abf80 RCX: 00007f481d28c389
RDX: 00000000000001ff RSI: 0000000020000000 RDI: ffffffffffffff9c
RBP: 00007f481d2d7493 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffed0ce2f4f R14: 00007f481df7d300 R15: 0000000000022000
 </TASK>