From: syzbot <syzbot+list84373195a560045a1095@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 (Mar 2026)
Date: Sat, 28 Feb 2026 22:22:31 -0800 [thread overview]
Message-ID: <69a3db27.050a0220.3a55be.0051.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 1 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> 9729 Yes possible deadlock in run_unpack_ex
https://syzkaller.appspot.com/bug?extid=731b27ee9413ba859499
<2> 5669 Yes possible deadlock in ntfs_fiemap
https://syzkaller.appspot.com/bug?extid=96cee7d33ca3f87eee86
<3> 3708 Yes possible deadlock in attr_data_get_block (2)
https://syzkaller.appspot.com/bug?extid=262a71e9d2faf8747085
<4> 522 Yes possible deadlock in ntfs_fallocate
https://syzkaller.appspot.com/bug?extid=adacb2b0c896bc427962
<5> 135 Yes WARNING in ni_rename (2)
https://syzkaller.appspot.com/bug?extid=4d8e30dbafb5c1260479
<6> 14 Yes WARNING in wnd_add_free_ext (4)
https://syzkaller.appspot.com/bug?extid=323f07d372f692a127b3
<7> 5 Yes WARNING in attr_data_get_block_locked
https://syzkaller.appspot.com/bug?extid=c1e9aedbd913fadad617
---
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-03-01 6:22 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=69a3db27.050a0220.3a55be.0051.GAE@google.com \
--to=syzbot+list84373195a560045a1095@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