From: syzbot <syzbot+list1c844d77bd05e3197946@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly hfs report (May 2024)
Date: Mon, 13 May 2024 14:13:22 -0700 [thread overview]
Message-ID: <000000000000fdbce606185c5a83@google.com> (raw)
Hello hfs maintainers/developers,
This is a 31-day syzbot report for the hfs subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/hfs
During the period, 2 new issues were detected and 0 were fixed.
In total, 43 issues are still open and 16 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 35302 Yes possible deadlock in hfsplus_file_truncate
https://syzkaller.appspot.com/bug?extid=6030b3b1b9bf70e538c4
<2> 23022 Yes possible deadlock in hfsplus_file_extend
https://syzkaller.appspot.com/bug?extid=325b61d3c9a17729454b
<3> 10227 Yes KASAN: slab-out-of-bounds Read in generic_perform_write
https://syzkaller.appspot.com/bug?extid=4a2376bc62e59406c414
<4> 8676 Yes possible deadlock in hfsplus_get_block
https://syzkaller.appspot.com/bug?extid=b7ef7c0c8d8098686ae2
<5> 6584 Yes KMSAN: uninit-value in hfs_revalidate_dentry
https://syzkaller.appspot.com/bug?extid=3ae6be33a50b5aae4dab
<6> 4613 Yes kernel BUG in __hfsplus_setxattr
https://syzkaller.appspot.com/bug?extid=1107451c16b9eb9d29e6
<7> 2337 Yes kernel BUG in hfs_write_inode
https://syzkaller.appspot.com/bug?extid=97e301b4b82ae803d21b
<8> 1254 Yes WARNING in drop_nlink (2)
https://syzkaller.appspot.com/bug?extid=651ca866e5e2b4b5095b
<9> 1102 Yes KASAN: slab-out-of-bounds Read in hfsplus_uni2asc
https://syzkaller.appspot.com/bug?extid=076d963e115823c4b9be
<10> 877 Yes KMSAN: uninit-value in hfsplus_delete_cat
https://syzkaller.appspot.com/bug?extid=fdedff847a0e5e84c39f
---
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-05-13 21:13 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=000000000000fdbce606185c5a83@google.com \
--to=syzbot+list1c844d77bd05e3197946@syzkaller.appspotmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).