From: syzbot <syzbot+list46ee6100e7a589a627ec@syzkaller.appspotmail.com>
To: anton@tuxera.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly ntfs report (Dec 2023)
Date: Wed, 06 Dec 2023 02:05:22 -0800 [thread overview]
Message-ID: <00000000000045d4c4060bd47dc6@google.com> (raw)
Hello ntfs maintainers/developers,
This is a 31-day syzbot report for the ntfs subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/ntfs
During the period, 0 new issues were detected and 0 were fixed.
In total, 25 issues are still open and 8 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 4839 Yes possible deadlock in ntfs_read_folio
https://syzkaller.appspot.com/bug?extid=8ef76b0b1f86c382ad37
<2> 3503 Yes kernel BUG at fs/ntfs/aops.c:LINE!
https://syzkaller.appspot.com/bug?extid=6a5a7672f663cce8b156
<3> 1691 Yes kernel BUG in __ntfs_grab_cache_pages
https://syzkaller.appspot.com/bug?extid=01b3ade7c86f7dd584d7
<4> 763 Yes possible deadlock in map_mft_record
https://syzkaller.appspot.com/bug?extid=cb1fdea540b46f0ce394
<5> 416 Yes KASAN: slab-out-of-bounds Read in ntfs_readdir
https://syzkaller.appspot.com/bug?extid=d36761079ac1b585a6df
<6> 312 Yes kernel BUG at fs/inode.c:LINE! (2)
https://syzkaller.appspot.com/bug?extid=c92c93d1f1aaaacdb9db
<7> 290 No possible deadlock in __ntfs_clear_inode
https://syzkaller.appspot.com/bug?extid=5ebb8d0e9b8c47867596
<8> 55 Yes kernel BUG in ntfs_iget
https://syzkaller.appspot.com/bug?extid=d62e6bd2a2d05103d105
<9> 39 Yes kernel BUG in ntfs_lookup_inode_by_name
https://syzkaller.appspot.com/bug?extid=d532380eef771ac0034b
<10> 19 Yes KASAN: use-after-free Read in ntfs_attr_find (2)
https://syzkaller.appspot.com/bug?extid=ef50f8eb00b54feb7ba2
---
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:[~2023-12-06 10:05 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=00000000000045d4c4060bd47dc6@google.com \
--to=syzbot+list46ee6100e7a589a627ec@syzkaller.appspotmail.com \
--cc=anton@tuxera.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--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;
as well as URLs for NNTP newsgroup(s).