From: syzbot <syzbot+list1e64672c7831f2f46cc6@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 (Nov 2026)
Date: Fri, 06 Nov 2026 04:33:48 -0800 [thread overview]
Message-ID: <6aedc92c.a716b02e.a4a62.0002.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, 17 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> 11662 Yes WARNING in hfs_bnode_create
https://syzkaller.appspot.com/bug?extid=a19ca73b21fe8bc69101
<2> 8181 Yes possible deadlock in hfs_find_init (2)
https://syzkaller.appspot.com/bug?extid=e390d66dda462b51fde1
<3> 1125 Yes possible deadlock in hfsplus_find_init
https://syzkaller.appspot.com/bug?extid=f8ce6c197125ab9d72ce
<4> 6122 Yes possible deadlock in hfs_extend_file (3)
https://syzkaller.appspot.com/bug?extid=2a62f58f1a4951a549bb
<5> 1895 Yes KMSAN: uninit-value in hfsplus_rename_cat
https://syzkaller.appspot.com/bug?extid=93f4402297a457fc6895
<6> 1121 Yes possible deadlock in hfsplus_file_extend (2)
https://syzkaller.appspot.com/bug?extid=4cba2fd444e9a16ae758
---
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-11-06 12: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=6aedc92c.a716b02e.a4a62.0002.GAE@google.com \
--to=syzbot+list1e64672c7831f2f46cc6@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 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.