From: syzbot <syzbot+list6b6c0ded30f354a11c3c@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly hfs report (Jan 2025)
Date: Mon, 20 Jan 2025 00:15:24 -0800 [thread overview]
Message-ID: <678e061c.050a0220.303755.0071.GAE@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, 1 new issues were detected and 0 were fixed.
In total, 45 issues are still open and 22 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 50656 Yes kernel BUG in hfs_write_inode
https://syzkaller.appspot.com/bug?extid=97e301b4b82ae803d21b
<2> 13133 Yes kernel BUG in __hfsplus_setxattr
https://syzkaller.appspot.com/bug?extid=1107451c16b9eb9d29e6
<3> 12001 Yes possible deadlock in hfsplus_get_block
https://syzkaller.appspot.com/bug?extid=b7ef7c0c8d8098686ae2
<4> 4274 Yes KMSAN: uninit-value in hfsplus_cat_case_cmp_key
https://syzkaller.appspot.com/bug?extid=50d8672fea106e5387bb
<5> 2638 Yes possible deadlock in hfs_find_init (2)
https://syzkaller.appspot.com/bug?extid=e390d66dda462b51fde1
<6> 2500 Yes KMSAN: uninit-value in hfsplus_delete_cat
https://syzkaller.appspot.com/bug?extid=fdedff847a0e5e84c39f
<7> 2483 Yes KASAN: slab-out-of-bounds Read in hfsplus_uni2asc
https://syzkaller.appspot.com/bug?extid=076d963e115823c4b9be
<8> 2461 Yes KMSAN: uninit-value in hfs_find_set_zero_bits
https://syzkaller.appspot.com/bug?extid=773fa9d79b29bd8b6831
<9> 2358 Yes KMSAN: uninit-value in hfsplus_attr_bin_cmp_key
https://syzkaller.appspot.com/bug?extid=c6d8e1bffb0970780d5c
<10> 2228 Yes KMSAN: uninit-value in hfsplus_lookup
https://syzkaller.appspot.com/bug?extid=91db973302e7b18c7653
---
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:[~2025-01-20 8:15 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=678e061c.050a0220.303755.0071.GAE@google.com \
--to=syzbot+list6b6c0ded30f354a11c3c@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