============================================
WARNING: possible recursive locking detected
4.19.211-syzkaller #0 Not tainted
--------------------------------------------
syz-executor.1/10797 is trying to acquire lock:
00000000bf27d4be (&type->i_mutex_dir_key#11){++++}, at: inode_lock include/linux/fs.h:748 [inline]
00000000bf27d4be (&type->i_mutex_dir_key#11){++++}, at: fuse_reverse_inval_entry+0x2e1/0x660 fs/fuse/dir.c:1006

but task is already holding lock:
00000000de5ee0c7 (&type->i_mutex_dir_key#11){++++}, at: inode_lock include/linux/fs.h:748 [inline]
00000000de5ee0c7 (&type->i_mutex_dir_key#11){++++}, at: fuse_reverse_inval_entry+0xaa/0x660 fs/fuse/dir.c:987

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(&type->i_mutex_dir_key#11);
  lock(&type->i_mutex_dir_key#11);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

2 locks held by syz-executor.1/10797:
 #0: 000000003c2a2591 (&fc->killsb){++++}, at: fuse_notify_delete fs/fuse/dev.c:1582 [inline]
 #0: 000000003c2a2591 (&fc->killsb){++++}, at: fuse_notify fs/fuse/dev.c:1819 [inline]
 #0: 000000003c2a2591 (&fc->killsb){++++}, at: fuse_dev_do_write+0x2343/0x2bc0 fs/fuse/dev.c:1894
 #1: 00000000de5ee0c7 (&type->i_mutex_dir_key#11){++++}, at: inode_lock include/linux/fs.h:748 [inline]
 #1: 00000000de5ee0c7 (&type->i_mutex_dir_key#11){++++}, at: fuse_reverse_inval_entry+0xaa/0x660 fs/fuse/dir.c:987

stack backtrace:
CPU: 0 PID: 10797 Comm: syz-executor.1 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
 print_deadlock_bug kernel/locking/lockdep.c:1764 [inline]
 check_deadlock kernel/locking/lockdep.c:1808 [inline]
 validate_chain kernel/locking/lockdep.c:2404 [inline]
 __lock_acquire.cold+0x121/0x57e kernel/locking/lockdep.c:3416
 lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3908
 down_write+0x34/0x90 kernel/locking/rwsem.c:70
 inode_lock include/linux/fs.h:748 [inline]
 fuse_reverse_inval_entry+0x2e1/0x660 fs/fuse/dir.c:1006
 fuse_notify_delete fs/fuse/dev.c:1585 [inline]
 fuse_notify fs/fuse/dev.c:1819 [inline]
 fuse_dev_do_write+0x239e/0x2bc0 fs/fuse/dev.c:1894
 fuse_dev_write+0x153/0x1e0 fs/fuse/dev.c:1978
IPVS: ftp: loaded support on port[0] = 21
 call_write_iter include/linux/fs.h:1821 [inline]
 new_sync_write fs/read_write.c:474 [inline]
 __vfs_write+0x51b/0x770 fs/read_write.c:487
 vfs_write+0x1f3/0x540 fs/read_write.c:549
 ksys_write+0x12b/0x2a0 fs/read_write.c:599
 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f21bea130d9
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:00007f21bcf64168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f21beb33050 RCX: 00007f21bea130d9
RDX: 000000000000002a RSI: 0000000020000080 RDI: 0000000000000003
RBP: 00007f21bea6eae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fffed78e81f R14: 00007f21bcf64300 R15: 0000000000022000
IPVS: ftp: loaded support on port[0] = 21
IPVS: ftp: loaded support on port[0] = 21
f2fs_msg: 10 callbacks suppressed
F2FS-fs (loop4): Invalid log sectors per block(2411855875) log sectorsize(9)
F2FS-fs (loop4): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (loop4): invalid crc value
F2FS-fs (loop4): Found nat_bits in checkpoint
F2FS-fs (loop4): Mounted with checkpoint version = 753bd00b
audit: type=1800 audit(1671563039.957:17): pid=10790 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=collect_data cause=failed(directio) comm="syz-executor.4" name="bus" dev="loop4" ino=6 res=0
F2FS-fs (loop3): Invalid log sectors per block(2411855875) log sectorsize(9)
F2FS-fs (loop3): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (loop3): invalid crc value
F2FS-fs (loop3): Found nat_bits in checkpoint
F2FS-fs (loop3): Mounted with checkpoint version = 753bd00b
audit: type=1800 audit(1671563042.187:18): pid=10952 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=collect_data cause=failed(directio) comm="syz-executor.5" name="bus" dev="loop5" ino=6 res=0
audit: type=1800 audit(1671563042.397:19): pid=10957 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=collect_data cause=failed(directio) comm="syz-executor.4" name="bus" dev="loop4" ino=6 res=0
IPVS: ftp: loaded support on port[0] = 21
audit: type=1800 audit(1671563043.987:20): pid=11002 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=collect_data cause=failed(directio) comm="syz-executor.3" name="bus" dev="loop3" ino=6 res=0
Cannot find add_set index 0 as target
ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
Cannot find add_set index 0 as target
Cannot find add_set index 0 as target
Cannot find add_set index 0 as target
tpacket_rcv: packet too big, clamped from 65007 to 32638. macoff=82