From: syzbot <syzbot+list782c9445342e49a6357c@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 (Dec 2023)
Date: Sat, 02 Dec 2023 06:45:22 -0800 [thread overview]
Message-ID: <0000000000003a2370060b87efc3@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, 57 issues are still open and 28 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 11352 Yes VFS: Busy inodes after unmount (use-after-free)
https://syzkaller.appspot.com/bug?extid=0af00f6a2cba2058b5db
<2> 3624 Yes KASAN: slab-out-of-bounds Read in ntfs_iget5
https://syzkaller.appspot.com/bug?extid=b4084c18420f9fad0b4f
<3> 2143 Yes possible deadlock in ni_fiemap
https://syzkaller.appspot.com/bug?extid=c300ab283ba3bc072439
<4> 1875 Yes KASAN: out-of-bounds Write in end_buffer_read_sync
https://syzkaller.appspot.com/bug?extid=3f7f291a3d327486073c
<5> 1451 Yes possible deadlock in attr_data_get_block
https://syzkaller.appspot.com/bug?extid=36bb70085ef6edc2ebb9
<6> 1359 Yes possible deadlock in ntfs_set_state
https://syzkaller.appspot.com/bug?extid=f91c29a5d5a01ada051a
<7> 691 Yes possible deadlock in mi_read
https://syzkaller.appspot.com/bug?extid=bc7ca0ae4591cb2550f9
<8> 550 Yes possible deadlock in filemap_fault
https://syzkaller.appspot.com/bug?extid=7736960b837908f3a81d
<9> 527 Yes possible deadlock in ntfs_fiemap
https://syzkaller.appspot.com/bug?extid=96cee7d33ca3f87eee86
<10> 311 Yes kernel BUG at fs/inode.c:LINE! (2)
https://syzkaller.appspot.com/bug?extid=c92c93d1f1aaaacdb9db
---
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-02 14:45 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=0000000000003a2370060b87efc3@google.com \
--to=syzbot+list782c9445342e49a6357c@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.