From: syzbot <syzbot+list1bd93f1b2a6555c648f2@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly fs report (Jun 2026)
Date: Tue, 09 Jun 2026 13:32:32 -0700 [thread overview]
Message-ID: <6a287860.39669fcc.33b062.009e.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, 4 new issues were detected and 0 were fixed.
In total, 45 issues are still open and 633 have already been fixed.
There are also 12 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 7729 Yes INFO: task hung in __iterate_supers
https://syzkaller.appspot.com/bug?extid=b10aefdd9ef275e9368d
<2> 3765 Yes INFO: task hung in synchronize_rcu (4)
https://syzkaller.appspot.com/bug?extid=222aa26d0a5dbc2e84fe
<3> 2673 Yes INFO: task hung in filename_create (4)
https://syzkaller.appspot.com/bug?extid=72c5cf124089bc318016
<4> 1652 Yes INFO: task hung in user_get_super (2)
https://syzkaller.appspot.com/bug?extid=ba09f4a317431df6cddf
<5> 196 No possible deadlock in kbd_event
https://syzkaller.appspot.com/bug?extid=781c8bb5e4d62cc883d3
<6> 79 Yes UBSAN: shift-out-of-bounds in befs_check_sb
https://syzkaller.appspot.com/bug?extid=fc26c366038b54261e53
<7> 7522 Yes possible deadlock in input_event (2)
https://syzkaller.appspot.com/bug?extid=d4c06e848a1c1f9f726f
<8> 4862 Yes INFO: task hung in path_openat (7)
https://syzkaller.appspot.com/bug?extid=950a0cdaa2fdd14f5bdc
<9> 160 Yes INFO: rcu detected stall in sys_clock_adjtime
https://syzkaller.appspot.com/bug?extid=25b7addb06e92c482190
<10> 101 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-06-09 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=6a287860.39669fcc.33b062.009e.GAE@google.com \
--to=syzbot+list1bd93f1b2a6555c648f2@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
Powered by JetHome