From: syzbot <syzbot+listcd973ab20f45b5fb0d7d@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 (Jan 2026)
Date: Wed, 28 Jan 2026 14:39:36 -0800 [thread overview]
Message-ID: <697a9028.a70a0220.9914.000c.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, 1 new issues were detected and 1 were fixed.
In total, 20 issues are still open and 82 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 9370 Yes possible deadlock in run_unpack_ex
https://syzkaller.appspot.com/bug?extid=731b27ee9413ba859499
<2> 5594 Yes possible deadlock in ntfs_fiemap
https://syzkaller.appspot.com/bug?extid=96cee7d33ca3f87eee86
<3> 3616 Yes possible deadlock in attr_data_get_block (2)
https://syzkaller.appspot.com/bug?extid=262a71e9d2faf8747085
<4> 517 Yes possible deadlock in ntfs_fallocate
https://syzkaller.appspot.com/bug?extid=adacb2b0c896bc427962
<5> 411 Yes possible deadlock in mi_read (2)
https://syzkaller.appspot.com/bug?extid=17f812893d5906837f33
<6> 137 Yes KMSAN: uninit-value in iov_iter_alignment_iovec
https://syzkaller.appspot.com/bug?extid=f2a9c06bfaa027217ebb
<7> 116 Yes WARNING in ni_rename (2)
https://syzkaller.appspot.com/bug?extid=4d8e30dbafb5c1260479
<8> 88 Yes WARNING in do_symlinkat (2)
https://syzkaller.appspot.com/bug?extid=d123d9a1df4f9a897854
<9> 15 Yes WARNING in errseq_set (2)
https://syzkaller.appspot.com/bug?extid=57f9327d593d301ce2a2
<10> 15 Yes WARNING in iov_iter_revert (5)
https://syzkaller.appspot.com/bug?extid=1e5f71cac2c1db825478
---
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-01-28 22:39 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=697a9028.a70a0220.9914.000c.GAE@google.com \
--to=syzbot+listcd973ab20f45b5fb0d7d@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