From: syzbot <syzbot+list44e13f647c7f62aaab25@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 (Apr 2026)
Date: Wed, 01 Apr 2026 00:42:23 -0700 [thread overview]
Message-ID: <69cccc5f.050a0220.183828.003d.GAE@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, 2 new issues were detected and 0 were fixed.
In total, 20 issues are still open and 88 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 438 Yes possible deadlock in mi_read (2)
https://syzkaller.appspot.com/bug?extid=17f812893d5906837f33
<2> 153 Yes WARNING in ni_rename (2)
https://syzkaller.appspot.com/bug?extid=4d8e30dbafb5c1260479
<3> 20 Yes WARNING in errseq_set (2)
https://syzkaller.appspot.com/bug?extid=57f9327d593d301ce2a2
<4> 18 Yes WARNING in iov_iter_revert (5)
https://syzkaller.appspot.com/bug?extid=1e5f71cac2c1db825478
<5> 15 Yes WARNING in wnd_add_free_ext (4)
https://syzkaller.appspot.com/bug?extid=323f07d372f692a127b3
<6> 6 Yes INFO: task hung in ntfs_fallocate
https://syzkaller.appspot.com/bug?extid=3829f3f96d42c57315fe
<7> 1 No KASAN: slab-use-after-free Read in ntfs_iget5
https://syzkaller.appspot.com/bug?extid=4d48dcd9e88d37df77b3
---
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:[~2026-04-01 7:42 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=69cccc5f.050a0220.183828.003d.GAE@google.com \
--to=syzbot+list44e13f647c7f62aaab25@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