From: syzbot <syzbot+list6ec5971c0fd039e92cbd@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly ntfs3 report (Sep 2024)
Date: Thu, 12 Sep 2024 01:11:21 -0700 [thread overview]
Message-ID: <000000000000e831e90621e7a6b5@google.com> (raw)
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, 12 new issues were detected and 0 were fixed.
In total, 38 issues are still open and 50 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 12022 Yes VFS: Busy inodes after unmount (use-after-free)
https://syzkaller.appspot.com/bug?extid=0af00f6a2cba2058b5db
<2> 8882 Yes possible deadlock in mi_read
https://syzkaller.appspot.com/bug?extid=bc7ca0ae4591cb2550f9
<3> 6470 Yes kernel BUG in dnotify_free_mark
https://syzkaller.appspot.com/bug?extid=06cc05ddc896f12b7ec5
<4> 3596 Yes KASAN: out-of-bounds Write in end_buffer_read_sync
https://syzkaller.appspot.com/bug?extid=3f7f291a3d327486073c
<5> 1828 Yes possible deadlock in ntfs_fiemap
https://syzkaller.appspot.com/bug?extid=96cee7d33ca3f87eee86
<6> 864 Yes possible deadlock in ntfs_file_mmap
https://syzkaller.appspot.com/bug?extid=c1751b6739d83d70bb75
<7> 491 Yes possible deadlock in attr_data_get_block (2)
https://syzkaller.appspot.com/bug?extid=262a71e9d2faf8747085
<8> 179 Yes possible deadlock in ntfs_fallocate
https://syzkaller.appspot.com/bug?extid=adacb2b0c896bc427962
<9> 83 Yes possible deadlock in ntfs_mark_rec_free (2)
https://syzkaller.appspot.com/bug?extid=016b09736213e65d106e
<10> 56 Yes KMSAN: uninit-value in ntfs_read_bh
https://syzkaller.appspot.com/bug?extid=7a2ba6b7b66340cff225
---
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@googlegroups.com.
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.
reply other threads:[~2024-09-12 8:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000e831e90621e7a6b5@google.com \
--to=syzbot+list6ec5971c0fd039e92cbd@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox