From: syzbot <syzbot+list32a9ebc8ed81539e58eb@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 (Jun 2025)
Date: Tue, 24 Jun 2025 00:38:27 -0700 [thread overview]
Message-ID: <685a55f3.050a0220.2303ee.0006.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, 39 issues are still open and 65 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 20874 Yes kernel BUG in dnotify_free_mark
https://syzkaller.appspot.com/bug?extid=06cc05ddc896f12b7ec5
<2> 14296 Yes KMSAN: uninit-value in longest_match_std (2)
https://syzkaller.appspot.com/bug?extid=08d8956768c96a2c52cf
<3> 5925 Yes possible deadlock in run_unpack_ex
https://syzkaller.appspot.com/bug?extid=731b27ee9413ba859499
<4> 5556 Yes possible deadlock in ntfs_read_folio
https://syzkaller.appspot.com/bug?extid=8ef76b0b1f86c382ad37
<5> 4757 Yes KASAN: out-of-bounds Write in end_buffer_read_sync
https://syzkaller.appspot.com/bug?extid=3f7f291a3d327486073c
<6> 4422 Yes possible deadlock in ntfs_fiemap
https://syzkaller.appspot.com/bug?extid=96cee7d33ca3f87eee86
<7> 3268 Yes possible deadlock in ntfs_file_mmap
https://syzkaller.appspot.com/bug?extid=c1751b6739d83d70bb75
<8> 2667 Yes possible deadlock in mark_as_free_ex (2)
https://syzkaller.appspot.com/bug?extid=8df514c431bd240c5644
<9> 2331 Yes possible deadlock in ntfs_look_for_free_space
https://syzkaller.appspot.com/bug?extid=d27edf9f96ae85939222
<10> 2329 Yes possible deadlock in attr_data_get_block (2)
https://syzkaller.appspot.com/bug?extid=262a71e9d2faf8747085
---
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-06-24 7:38 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=685a55f3.050a0220.2303ee.0006.GAE@google.com \
--to=syzbot+list32a9ebc8ed81539e58eb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.