From: syzbot <syzbot+list2e977b7855a334fac744@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly fs report (Nov 2026)
Date: Thu, 12 Nov 2026 12:33:56 -0800 [thread overview]
Message-ID: <6af622b4.ff6dfe28.557e.0019.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 644 have already been fixed.
There are also 35 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 12025 Yes KASAN: use-after-free Read in hpfs_get_ea
https://syzkaller.appspot.com/bug?extid=fa88eb476e42878f2844
<2> 10568 Yes VFS: Busy inodes after unmount (use-after-free) (4)
https://syzkaller.appspot.com/bug?extid=d569e274f46ca86f78fa
<3> 8841 Yes INFO: task hung in __iterate_supers
https://syzkaller.appspot.com/bug?extid=b10aefdd9ef275e9368d
<4> 2045 Yes INFO: task hung in user_get_super (2)
https://syzkaller.appspot.com/bug?extid=ba09f4a317431df6cddf
<5> 37 Yes KASAN: slab-use-after-free Read in lockref_get (2)
https://syzkaller.appspot.com/bug?extid=227dbc9afd022922d624
<6> 28 Yes INFO: rcu detected stall in sys_close (7)
https://syzkaller.appspot.com/bug?extid=393022c13d02e1f680e3
<7> 26 Yes INFO: task hung in writeback_iter (3)
https://syzkaller.appspot.com/bug?extid=1e3ff4b07c16ca0f6fe2
<8> 11 Yes KASAN: use-after-free Read in hpfs_bplus_lookup
https://syzkaller.appspot.com/bug?extid=8debf4b3f7c7391cd8eb
<9> 11 Yes divide error in qnx6_mmi_fill_super
https://syzkaller.appspot.com/bug?extid=6a0633f11d3fb88860bf
<10> 10 Yes INFO: rcu detected stall in kswapd (4)
https://syzkaller.appspot.com/bug?extid=f886305df0acc6fa097a
---
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-12 20: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=6af622b4.ff6dfe28.557e.0019.GAE@google.com \
--to=syzbot+list2e977b7855a334fac744@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