============================================ WARNING: possible recursive locking detected 4.19.211-syzkaller #0 Not tainted -------------------------------------------- syz-executor.5/13203 is trying to acquire lock: 00000000072fbab9 (&type->i_mutex_dir_key#9){++++}, at: inode_lock include/linux/fs.h:748 [inline] 00000000072fbab9 (&type->i_mutex_dir_key#9){++++}, at: fuse_reverse_inval_entry+0x2e1/0x660 fs/fuse/dir.c:1006 but task is already holding lock: 00000000c87d99fb (&type->i_mutex_dir_key#9){++++}, at: inode_lock include/linux/fs.h:748 [inline] 00000000c87d99fb (&type->i_mutex_dir_key#9){++++}, 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#9); lock(&type->i_mutex_dir_key#9); *** DEADLOCK *** May be due to missing lock nesting notation 2 locks held by syz-executor.5/13203: #0: 00000000ff7f39dd (&fc->killsb){.+.+}, at: fuse_notify_delete fs/fuse/dev.c:1582 [inline] #0: 00000000ff7f39dd (&fc->killsb){.+.+}, at: fuse_notify fs/fuse/dev.c:1819 [inline] #0: 00000000ff7f39dd (&fc->killsb){.+.+}, at: fuse_dev_do_write+0x2343/0x2bc0 fs/fuse/dev.c:1894 #1: 00000000c87d99fb (&type->i_mutex_dir_key#9){++++}, at: inode_lock include/linux/fs.h:748 [inline] #1: 00000000c87d99fb (&type->i_mutex_dir_key#9){++++}, at: fuse_reverse_inval_entry+0xaa/0x660 fs/fuse/dir.c:987 stack backtrace: CPU: 0 PID: 13203 Comm: syz-executor.5 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/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 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:0x7f0ca6eb45a9 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 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f0ca5427168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007f0ca6fd4f80 RCX: 00007f0ca6eb45a9 RDX: 000000000000002c RSI: 00000000200000c0 RDI: 0000000000000003 RBP: 00007f0ca6f0f7b0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe44c8060f R14: 00007f0ca5427300 R15: 0000000000022000 audit: type=1804 audit(1667009475.760:15): pid=13223 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.4" name="/root/syzkaller-testdir1132961697/syzkaller.IRAcDM/111/bus" dev="sda1" ino=14283 res=1 audit: type=1804 audit(1667009476.120:16): pid=13259 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.4" name="/root/syzkaller-testdir1132961697/syzkaller.IRAcDM/112/bus" dev="sda1" ino=14291 res=1 audit: type=1804 audit(1667009476.210:17): pid=13269 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.2" name="/root/syzkaller-testdir3904429100/syzkaller.MCTh3o/134/bus" dev="sda1" ino=14048 res=1 audit: type=1804 audit(1667009476.290:18): pid=13268 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.4" name="/root/syzkaller-testdir1132961697/syzkaller.IRAcDM/113/bus" dev="sda1" ino=14291 res=1 GRED: Unable to relocate VQ 0x0 after dequeue, screwing up backlog audit: type=1804 audit(1667009476.340:19): pid=13286 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.2" name="/root/syzkaller-testdir3904429100/syzkaller.MCTh3o/135/bus" dev="sda1" ino=14276 res=1 device bond0 entered promiscuous mode audit: type=1804 audit(1667009476.420:20): pid=13292 uid=0 auid=4294967295 ses=4294967295 subj==unconfined op=invalid_pcr cause=open_writers comm="syz-executor.4" name="/root/syzkaller-testdir1132961697/syzkaller.IRAcDM/114/bus" dev="sda1" ino=14271 res=1 device bond_slave_0 entered promiscuous mode device  entered promiscuous mode L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. GRED: Unable to relocate VQ 0x0 after dequeue, screwing up backlog netlink: 12 bytes leftover after parsing attributes in process `syz-executor.2'. netlink: 12 bytes leftover after parsing attributes in process `syz-executor.2'. netlink: 12 bytes leftover after parsing attributes in process `syz-executor.5'. netlink: 12 bytes leftover after parsing attributes in process `syz-executor.4'. netlink: 12 bytes leftover after parsing attributes in process `syz-executor.3'. netlink: 12 bytes leftover after parsing attributes in process `syz-executor.2'. netlink: 12 bytes leftover after parsing attributes in process `syz-executor.5'. netlink: 12 bytes leftover after parsing attributes in process `syz-executor.2'. netlink: 12 bytes leftover after parsing attributes in process `syz-executor.4'. netlink: 12 bytes leftover after parsing attributes in process `syz-executor.3'. overlayfs: upper fs needs to support d_type. overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. overlayfs: failed to resolve './file0': -2 overlayfs: upper fs needs to support d_type. overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. overlayfs: upper fs needs to support d_type. overlayfs: upper fs needs to support d_type. overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. GRED: Unable to relocate VQ 0x0 after dequeue, screwing up backlog overlayfs: failed to resolve './file0': -2 overlayfs: failed to resolve './file0': -2 ieee802154 phy0 wpan0: encryption failed: -22 ieee802154 phy1 wpan1: encryption failed: -22 overlayfs: upper fs needs to support d_type. overlayfs: upper fs needs to support d_type. overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. overlayfs: failed to resolve './file0': -2 overlayfs: upper fs needs to support d_type. overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. overlayfs: failed to resolve './file0': -2 GRED: Unable to relocate VQ 0x0 after dequeue, screwing up backlog overlayfs: './file1' not a directory overlayfs: upper fs needs to support d_type. overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. overlayfs: upper fs needs to support d_type. overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. overlayfs: upper fs needs to support d_type. overlayfs: failed to resolve './file0': -2 overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. overlayfs: upper fs needs to support d_type. overlayfs: upper fs does not support xattr, falling back to index=off and metacopy=off. GRED: Unable to relocate VQ 0x0 after dequeue, screwing up backlog EXT4-fs (loop3): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs (loop1): mounting with "discard" option, but the device does not support discard EXT4-fs (loop1): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs (loop4): mounting with "discard" option, but the device does not support discard EXT4-fs (loop3): mounted filesystem without journal. Opts: ,errors=continue EXT4-fs (loop2): mounting with "discard" option, but the device does not support discard EXT4-fs (loop4): mounted filesystem without journal. Opts: ,errors=continue