From: syzbot <syzbot+list76209f953d5a6e865b37@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 (Nov 2025)
Date: Wed, 26 Nov 2025 23:44:29 -0800 [thread overview]
Message-ID: <6928015c.a70a0220.d98e3.00f5.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, 3 new issues were detected and 0 were fixed.
In total, 26 issues are still open and 70 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 8369 Yes possible deadlock in run_unpack_ex
https://syzkaller.appspot.com/bug?extid=731b27ee9413ba859499
<2> 5226 Yes possible deadlock in ntfs_fiemap
https://syzkaller.appspot.com/bug?extid=96cee7d33ca3f87eee86
<3> 3778 Yes possible deadlock in mark_as_free_ex (2)
https://syzkaller.appspot.com/bug?extid=8df514c431bd240c5644
<4> 3438 Yes possible deadlock in ntfs_look_for_free_space
https://syzkaller.appspot.com/bug?extid=d27edf9f96ae85939222
<5> 3182 Yes possible deadlock in attr_data_get_block (2)
https://syzkaller.appspot.com/bug?extid=262a71e9d2faf8747085
<6> 504 Yes possible deadlock in ntfs_fallocate
https://syzkaller.appspot.com/bug?extid=adacb2b0c896bc427962
<7> 403 Yes possible deadlock in mi_read (2)
https://syzkaller.appspot.com/bug?extid=17f812893d5906837f33
<8> 126 Yes INFO: task hung in do_unlinkat (5)
https://syzkaller.appspot.com/bug?extid=08b113332e19a9378dd5
<9> 31 Yes WARNING in ni_rename (2)
https://syzkaller.appspot.com/bug?extid=4d8e30dbafb5c1260479
<10> 15 Yes WARNING in walk_component
https://syzkaller.appspot.com/bug?extid=eba014ac93ef29f83dc8
---
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:[~2025-11-27 7:44 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=6928015c.a70a0220.d98e3.00f5.GAE@google.com \
--to=syzbot+list76209f953d5a6e865b37@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