Hello ntfs3 maintainers/developers, This is a 31-day syzbot report for the ntfs3 subsystem. All related reports/information can be found at: https://syzkaller.appspot.com/upstream/s/ntfs3 During the period, 1 new issues were detected and 0 were fixed. In total, 35 issues are still open and 49 have been fixed so far. Some of the still happening issues: Ref Crashes Repro Title <1> 11997 Yes VFS: Busy inodes after unmount (use-after-free) https://syzkaller.appspot.com/bug?extid=0af00f6a2cba2058b5db <2> 6681 Yes possible deadlock in mi_read https://syzkaller.appspot.com/bug?extid=bc7ca0ae4591cb2550f9 <3> 5512 Yes possible deadlock in ntfs_read_folio https://syzkaller.appspot.com/bug?extid=8ef76b0b1f86c382ad37 <4> 4793 Yes kernel BUG in dnotify_free_mark https://syzkaller.appspot.com/bug?extid=06cc05ddc896f12b7ec5 <5> 4007 Yes possible deadlock in ni_fiemap https://syzkaller.appspot.com/bug?extid=c300ab283ba3bc072439 <6> 3561 Yes KASAN: out-of-bounds Write in end_buffer_read_sync https://syzkaller.appspot.com/bug?extid=3f7f291a3d327486073c <7> 1198 Yes possible deadlock in ntfs_fiemap https://syzkaller.appspot.com/bug?extid=96cee7d33ca3f87eee86 <8> 636 Yes possible deadlock in ntfs_set_state (2) https://syzkaller.appspot.com/bug?extid=c2ada45c23d98d646118 <9> 338 Yes possible deadlock in ntfs_file_mmap https://syzkaller.appspot.com/bug?extid=c1751b6739d83d70bb75 <10> 112 No possible deadlock in ntfs_fallocate https://syzkaller.appspot.com/bug?extid=adacb2b0c896bc427962 --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@xxxxxxxxxxxxxxxx. To disable reminders for individual bugs, reply with the following command: #syz set <Ref> no-reminders To change bug's subsystems, reply with: #syz set <Ref> subsystems: new-subsystem You may send multiple commands in a single email message.