From: syzbot <syzbot+list1d8e27291d051da3b6be@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly ntfs3 report (Apr 2023)
Date: Fri, 28 Apr 2023 01:47:46 -0700 [thread overview]
Message-ID: <000000000000faf54f05fa6186db@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, 8 new issues were detected and 0 were fixed.
In total, 62 issues are still open and 21 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3546 Yes KASAN: slab-out-of-bounds Read in ntfs_iget5
https://syzkaller.appspot.com/bug?extid=b4084c18420f9fad0b4f
<2> 1835 Yes UBSAN: shift-out-of-bounds in ntfs_fill_super (2)
https://syzkaller.appspot.com/bug?extid=478c1bf0e6bf4a8f3a04
<3> 1013 Yes KASAN: out-of-bounds Write in end_buffer_read_sync
https://syzkaller.appspot.com/bug?extid=3f7f291a3d327486073c
<4> 843 Yes possible deadlock in attr_data_get_block
https://syzkaller.appspot.com/bug?extid=36bb70085ef6edc2ebb9
<5> 388 Yes possible deadlock in ntfs_set_state
https://syzkaller.appspot.com/bug?extid=f91c29a5d5a01ada051a
<6> 352 Yes possible deadlock in mi_read
https://syzkaller.appspot.com/bug?extid=bc7ca0ae4591cb2550f9
<7> 242 No possible deadlock in ntfs_mark_rec_free
https://syzkaller.appspot.com/bug?extid=f83f0dbef763c426e3cf
<8> 65 Yes WARNING in do_symlinkat
https://syzkaller.appspot.com/bug?extid=e78eab0c1cf4649256ed
<9> 58 Yes KASAN: vmalloc-out-of-bounds Write in find_lock_entries
https://syzkaller.appspot.com/bug?extid=e498ebacfd2fd78cf7b2
<10> 51 Yes WARNING in do_mkdirat
https://syzkaller.appspot.com/bug?extid=919c5a9be8433b8bf201
---
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-04-28 8:47 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=000000000000faf54f05fa6186db@google.com \
--to=syzbot+list1d8e27291d051da3b6be@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--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.