From: syzbot <syzbot+list5a5fabbd60ac5aa4e76b@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
miklos@szeredi.hu, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly fuse report (Apr 2026)
Date: Fri, 10 Apr 2026 23:42:26 -0700 [thread overview]
Message-ID: <69d9ed52.a00a0220.475f0.0006.GAE@google.com> (raw)
Hello fuse maintainers/developers,
This is a 31-day syzbot report for the fuse subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/fuse
During the period, 3 new issues were detected and 0 were fixed.
In total, 8 issues are still open and 46 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 670 Yes INFO: task hung in __fuse_simple_request
https://syzkaller.appspot.com/bug?extid=0dbb0d6fda088e78a4d8
<2> 47 Yes INFO: task hung in fuse_lookup (3)
https://syzkaller.appspot.com/bug?extid=b64df836ad08c8e31a47
<3> 20 No linux-next test error: general protection fault in fuse_dev_alloc_install
https://syzkaller.appspot.com/bug?extid=9b639ce94c265f1daf1f
---
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-04-11 6:42 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=69d9ed52.a00a0220.475f0.0006.GAE@google.com \
--to=syzbot+list5a5fabbd60ac5aa4e76b@syzkaller.appspotmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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