From: syzbot <syzbot+list398bf1d226810d546c6e@syzkaller.appspotmail.com>
To: frank.li@vivo.com, glaubitz@physik.fu-berlin.de,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
slava@dubeyko.com, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly hfs report (Oct 2026)
Date: Mon, 05 Oct 2026 21:33:27 -0700 [thread overview]
Message-ID: <6ac47a17.598348e0.18b15.0008.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, 0 new issues were detected and 0 were fixed.
In total, 18 issues are still open and 42 have already been fixed.
There is also 1 low-priority issue.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 15760 Yes possible deadlock in hfsplus_get_block
https://syzkaller.appspot.com/bug?extid=b7ef7c0c8d8098686ae2
<2> 11266 Yes WARNING in hfs_bnode_create
https://syzkaller.appspot.com/bug?extid=a19ca73b21fe8bc69101
<3> 111 Yes INFO: task hung in deactivate_super (3)
https://syzkaller.appspot.com/bug?extid=cba6270878c89ed64a2d
<4> 17 Yes general protection fault in hfsplus_cat_write_inode
https://syzkaller.appspot.com/bug?extid=c0ba772a362e70937dfb
<5> 6037 Yes possible deadlock in hfs_extend_file (3)
https://syzkaller.appspot.com/bug?extid=2a62f58f1a4951a549bb
<6> 1887 Yes KMSAN: uninit-value in hfsplus_rename_cat
https://syzkaller.appspot.com/bug?extid=93f4402297a457fc6895
<7> 1059 Yes possible deadlock in hfsplus_file_extend (2)
https://syzkaller.appspot.com/bug?extid=4cba2fd444e9a16ae758
<8> 428 Yes possible deadlock in hfsplus_block_free
https://syzkaller.appspot.com/bug?extid=8fae81a1f77bf28ef3b5
<9> 19 Yes memory leak in __hfs_bnode_create
https://syzkaller.appspot.com/bug?extid=98547b0428b6a6a3467c
---
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:[~2026-10-06 4:33 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=6ac47a17.598348e0.18b15.0008.GAE@google.com \
--to=syzbot+list398bf1d226810d546c6e@syzkaller.appspotmail.com \
--cc=frank.li@vivo.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slava@dubeyko.com \
--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
all inboxes | Powered by JetHome®