From: syzbot <syzbot+list26922f6871252a2b2df9@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 2024)
Date: Mon, 16 Dec 2024 01:44:21 -0800 [thread overview]
Message-ID: <675ff675.050a0220.37aaf.0123.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, 4 new issues were detected and 0 were fixed.
In total, 45 issues are still open and 60 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 12409 Yes kernel BUG in dnotify_free_mark
https://syzkaller.appspot.com/bug?extid=06cc05ddc896f12b7ec5
<2> 9932 Yes KMSAN: uninit-value in longest_match_std (2)
https://syzkaller.appspot.com/bug?extid=08d8956768c96a2c52cf
<3> 5549 Yes possible deadlock in ntfs_read_folio
https://syzkaller.appspot.com/bug?extid=8ef76b0b1f86c382ad37
<4> 3925 Yes KASAN: out-of-bounds Write in end_buffer_read_sync
https://syzkaller.appspot.com/bug?extid=3f7f291a3d327486073c
<5> 3409 Yes possible deadlock in ntfs_fiemap
https://syzkaller.appspot.com/bug?extid=96cee7d33ca3f87eee86
<6> 1827 Yes possible deadlock in ntfs_file_mmap
https://syzkaller.appspot.com/bug?extid=c1751b6739d83d70bb75
<7> 1580 Yes possible deadlock in attr_data_get_block (2)
https://syzkaller.appspot.com/bug?extid=262a71e9d2faf8747085
<8> 1569 No possible deadlock in run_unpack_ex
https://syzkaller.appspot.com/bug?extid=731b27ee9413ba859499
<9> 1474 Yes kernel BUG in ntfs_extend_initialized_size
https://syzkaller.appspot.com/bug?extid=39385e8595a092bae44b
<10> 585 No possible deadlock in ntfs_look_for_free_space
https://syzkaller.appspot.com/bug?extid=d27edf9f96ae85939222
---
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:[~2024-12-16 9: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=675ff675.050a0220.37aaf.0123.GAE@google.com \
--to=syzbot+list26922f6871252a2b2df9@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