From: syzbot <syzbot+list0377cc5e08cc9b971109@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly fs report (Oct 2025)
Date: Fri, 31 Oct 2025 01:55:28 -0700 [thread overview]
Message-ID: <69047980.050a0220.e9cb8.0006.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, 5 new issues were detected and 1 were fixed.
In total, 59 issues are still open and 398 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 7013 Yes BUG: sleeping function called from invalid context in hook_sb_delete
https://syzkaller.appspot.com/bug?extid=12479ae15958fc3f54ec
<2> 6890 Yes WARNING in inc_nlink (3)
https://syzkaller.appspot.com/bug?extid=2b3af42c0644df1e4da9
<3> 6341 Yes possible deadlock in input_event (2)
https://syzkaller.appspot.com/bug?extid=d4c06e848a1c1f9f726f
<4> 4584 Yes INFO: task hung in path_openat (7)
https://syzkaller.appspot.com/bug?extid=950a0cdaa2fdd14f5bdc
<5> 4464 Yes BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio (4)
https://syzkaller.appspot.com/bug?extid=09b7d050e4806540153d
<6> 4309 Yes WARNING in path_noexec (2)
https://syzkaller.appspot.com/bug?extid=a9391462075ffb9f77c6
<7> 3776 Yes INFO: task hung in __iterate_supers
https://syzkaller.appspot.com/bug?extid=b10aefdd9ef275e9368d
<8> 3646 Yes INFO: task hung in page_cache_ra_unbounded (2)
https://syzkaller.appspot.com/bug?extid=265e1cae90f8fa08f14d
<9> 2852 Yes KASAN: use-after-free Read in hpfs_get_ea
https://syzkaller.appspot.com/bug?extid=fa88eb476e42878f2844
<10> 2314 Yes INFO: task hung in filename_create (4)
https://syzkaller.appspot.com/bug?extid=72c5cf124089bc318016
---
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:[~2025-10-31 8:55 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=69047980.050a0220.e9cb8.0006.GAE@google.com \
--to=syzbot+list0377cc5e08cc9b971109@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