From: syzbot <syzbot+list699b83da9318c0cd04e4@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
Date: Fri, 31 Mar 2023 08:00:45 -0700 [thread overview]
Message-ID: <00000000000045192105f8337955@google.com> (raw)
Hello ntfs maintainers/developers,
This is a 30-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, 4 new issues were detected and 0 were fixed.
In total, 22 issues are still open and 6 have been fixed so far.
Some of the still happening issues:
Crashes Repro Title
935 Yes possible deadlock in ntfs_read_folio
https://syzkaller.appspot.com/bug?extid=8ef76b0b1f86c382ad37
581 Yes kernel BUG in __ntfs_grab_cache_pages
https://syzkaller.appspot.com/bug?extid=01b3ade7c86f7dd584d7
261 No KASAN: use-after-free Read in ntfs_test_inode
https://syzkaller.appspot.com/bug?extid=2751da923b5eb8307b0b
171 Yes possible deadlock in map_mft_record
https://syzkaller.appspot.com/bug?extid=cb1fdea540b46f0ce394
112 No possible deadlock in __ntfs_clear_inode
https://syzkaller.appspot.com/bug?extid=5ebb8d0e9b8c47867596
77 Yes INFO: rcu detected stall in sys_mount (6)
https://syzkaller.appspot.com/bug?extid=ee7d095f44a683a195f8
4 Yes KASAN: use-after-free Read in ntfs_attr_find (2)
https://syzkaller.appspot.com/bug?extid=ef50f8eb00b54feb7ba2
4 Yes kernel BUG in ntfs_lookup_inode_by_name
https://syzkaller.appspot.com/bug?extid=d532380eef771ac0034b
2 Yes KASAN: use-after-free Read in ntfs_lookup_inode_by_name
https://syzkaller.appspot.com/bug?extid=3625b78845a725e80f61
---
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.
reply other threads:[~2023-03-31 15:01 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=00000000000045192105f8337955@google.com \
--to=syzbot+list699b83da9318c0cd04e4@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).