From: syzbot <syzbot+lista12ac4cc66e9ef5cbe7d@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 (Feb 2024)
Date: Fri, 02 Feb 2024 13:04:27 -0800 [thread overview]
Message-ID: <00000000000022908006106c7537@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, 1 new issues were detected and 0 were fixed.
In total, 54 issues are still open and 37 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 11637 Yes VFS: Busy inodes after unmount (use-after-free)
https://syzkaller.appspot.com/bug?extid=0af00f6a2cba2058b5db
<2> 5481 Yes possible deadlock in ntfs_read_folio
https://syzkaller.appspot.com/bug?extid=8ef76b0b1f86c382ad37
<3> 3804 Yes kernel BUG at fs/ntfs/aops.c:LINE!
https://syzkaller.appspot.com/bug?extid=6a5a7672f663cce8b156
<4> 2434 Yes possible deadlock in ni_fiemap
https://syzkaller.appspot.com/bug?extid=c300ab283ba3bc072439
<5> 2032 Yes KASAN: out-of-bounds Write in end_buffer_read_sync
https://syzkaller.appspot.com/bug?extid=3f7f291a3d327486073c
<6> 1926 Yes kernel BUG in __ntfs_grab_cache_pages
https://syzkaller.appspot.com/bug?extid=01b3ade7c86f7dd584d7
<7> 1668 Yes possible deadlock in attr_data_get_block
https://syzkaller.appspot.com/bug?extid=36bb70085ef6edc2ebb9
<8> 1289 Yes KMSAN: uninit-value in longest_match_std (2)
https://syzkaller.appspot.com/bug?extid=08d8956768c96a2c52cf
<9> 936 Yes possible deadlock in mi_read
https://syzkaller.appspot.com/bug?extid=bc7ca0ae4591cb2550f9
<10> 845 Yes possible deadlock in map_mft_record
https://syzkaller.appspot.com/bug?extid=cb1fdea540b46f0ce394
---
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-02-02 21:04 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=00000000000022908006106c7537@google.com \
--to=syzbot+lista12ac4cc66e9ef5cbe7d@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.