From: syzbot <syzbot+list59be5123a1c329b3c5e0@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 (Dec 2025)
Date: Mon, 29 Dec 2025 00:11:21 -0800 [thread overview]
Message-ID: <695237a9.a70a0220.c527.001d.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, 28 issues are still open and 74 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 22243 Yes KMSAN: uninit-value in longest_match_std (2)
https://syzkaller.appspot.com/bug?extid=08d8956768c96a2c52cf
<2> 8893 Yes possible deadlock in run_unpack_ex
https://syzkaller.appspot.com/bug?extid=731b27ee9413ba859499
<3> 5565 Yes possible deadlock in ntfs_read_folio
https://syzkaller.appspot.com/bug?extid=8ef76b0b1f86c382ad37
<4> 5410 Yes possible deadlock in ntfs_fiemap
https://syzkaller.appspot.com/bug?extid=96cee7d33ca3f87eee86
<5> 3847 Yes possible deadlock in mark_as_free_ex (2)
https://syzkaller.appspot.com/bug?extid=8df514c431bd240c5644
<6> 3394 Yes possible deadlock in attr_data_get_block (2)
https://syzkaller.appspot.com/bug?extid=262a71e9d2faf8747085
<7> 512 Yes possible deadlock in ntfs_fallocate
https://syzkaller.appspot.com/bug?extid=adacb2b0c896bc427962
<8> 407 Yes possible deadlock in mi_read (2)
https://syzkaller.appspot.com/bug?extid=17f812893d5906837f33
<9> 129 Yes INFO: task hung in do_unlinkat (5)
https://syzkaller.appspot.com/bug?extid=08b113332e19a9378dd5
<10> 122 Yes memory leak in ntfs_init_fs_context (2)
https://syzkaller.appspot.com/bug?extid=23aee7afc440fe803545
---
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-12-29 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=695237a9.a70a0220.c527.001d.GAE@google.com \
--to=syzbot+list59be5123a1c329b3c5e0@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