From: syzbot <syzbot+listb24c70845ff6f3242c14@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 (Jan 2024)
Date: Tue, 02 Jan 2024 05:36:28 -0800 [thread overview]
Message-ID: <000000000000e3a1c3060df6956c@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, 2 new issues were detected and 0 were fixed.
In total, 47 issues are still open and 28 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 11376 Yes VFS: Busy inodes after unmount (use-after-free)
https://syzkaller.appspot.com/bug?extid=0af00f6a2cba2058b5db
<2> 3629 Yes KASAN: slab-out-of-bounds Read in ntfs_iget5
https://syzkaller.appspot.com/bug?extid=b4084c18420f9fad0b4f
<3> 2282 Yes possible deadlock in ni_fiemap
https://syzkaller.appspot.com/bug?extid=c300ab283ba3bc072439
<4> 1943 Yes KASAN: out-of-bounds Write in end_buffer_read_sync
https://syzkaller.appspot.com/bug?extid=3f7f291a3d327486073c
<5> 1575 Yes possible deadlock in attr_data_get_block
https://syzkaller.appspot.com/bug?extid=36bb70085ef6edc2ebb9
<6> 826 No possible deadlock in ntfs_mark_rec_free
https://syzkaller.appspot.com/bug?extid=f83f0dbef763c426e3cf
<7> 775 Yes possible deadlock in mi_read
https://syzkaller.appspot.com/bug?extid=bc7ca0ae4591cb2550f9
<8> 583 Yes possible deadlock in ntfs_fiemap
https://syzkaller.appspot.com/bug?extid=96cee7d33ca3f87eee86
<9> 570 Yes possible deadlock in filemap_fault
https://syzkaller.appspot.com/bug?extid=7736960b837908f3a81d
<10> 312 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:[~2024-01-02 13:36 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=000000000000e3a1c3060df6956c@google.com \
--to=syzbot+listb24c70845ff6f3242c14@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).