From: syzbot <syzbot+list9e8c6407f4b6e9038ba2@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly fs report (Jul 2026)
Date: Fri, 10 Jul 2026 13:32:36 -0700 [thread overview]
Message-ID: <6a5156e4.278cdcd2.e885.0007.GAE@google.com> (raw)
Hello fs maintainers/developers,
This is a 31-day syzbot report for the fs subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/fs
During the period, 2 new issues were detected and 2 were fixed.
In total, 42 issues are still open and 636 have already been fixed.
There are also 11 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 8553 Yes INFO: task hung in __iterate_supers
https://syzkaller.appspot.com/bug?extid=b10aefdd9ef275e9368d
<2> 3998 Yes INFO: task hung in synchronize_rcu (4)
https://syzkaller.appspot.com/bug?extid=222aa26d0a5dbc2e84fe
<3> 2678 Yes INFO: task hung in filename_create (4)
https://syzkaller.appspot.com/bug?extid=72c5cf124089bc318016
<4> 2024 Yes INFO: task hung in user_get_super (2)
https://syzkaller.appspot.com/bug?extid=ba09f4a317431df6cddf
<5> 1998 Yes INFO: task hung in lookup_slow (3)
https://syzkaller.appspot.com/bug?extid=7cfc6a4f6b025f710423
<6> 209 Yes WARNING in path_openat
https://syzkaller.appspot.com/bug?extid=be8872fcb764bf9fea73
<7> 20 Yes INFO: task hung in writeback_iter (3)
https://syzkaller.appspot.com/bug?extid=1e3ff4b07c16ca0f6fe2
<8> 6 No possible deadlock in page_cache_ra_order
https://syzkaller.appspot.com/bug?extid=8bd419f88e25ab12cb75
<9> 2 Yes INFO: rcu detected stall in __fsnotify_parent (3)
https://syzkaller.appspot.com/bug?extid=27ce6cc06c1311c152f5
<10> 102 No INFO: rcu detected stall in blkdev_release (3)
https://syzkaller.appspot.com/bug?extid=07d6f9c5d7633ed4a5c8
---
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-07-10 20:32 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=6a5156e4.278cdcd2.e885.0007.GAE@google.com \
--to=syzbot+list9e8c6407f4b6e9038ba2@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 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.