From: syzbot <syzbot+listc95489547942700d4b48@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly fs report (Aug 2025)
Date: Fri, 29 Aug 2025 05:52:31 -0700 [thread overview]
Message-ID: <68b1a28f.a00a0220.1337b0.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, 3 new issues were detected and 0 were fixed.
In total, 62 issues are still open and 394 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 9318 Yes WARNING in path_noexec
https://syzkaller.appspot.com/bug?extid=3de83a9efcca3f0412ee
<2> 6870 Yes WARNING in inc_nlink (3)
https://syzkaller.appspot.com/bug?extid=2b3af42c0644df1e4da9
<3> 6225 Yes possible deadlock in input_event (2)
https://syzkaller.appspot.com/bug?extid=d4c06e848a1c1f9f726f
<4> 4523 Yes INFO: task hung in path_openat (7)
https://syzkaller.appspot.com/bug?extid=950a0cdaa2fdd14f5bdc
<5> 3643 Yes INFO: task hung in page_cache_ra_unbounded (2)
https://syzkaller.appspot.com/bug?extid=265e1cae90f8fa08f14d
<6> 3416 Yes BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio (4)
https://syzkaller.appspot.com/bug?extid=09b7d050e4806540153d
<7> 2812 Yes general protection fault in iter_file_splice_write
https://syzkaller.appspot.com/bug?extid=d2125fcb6aa8c4276fd2
<8> 2276 Yes INFO: task hung in filename_create (4)
https://syzkaller.appspot.com/bug?extid=72c5cf124089bc318016
<9> 1877 Yes INFO: task hung in lookup_slow (3)
https://syzkaller.appspot.com/bug?extid=7cfc6a4f6b025f710423
<10> 1485 Yes possible deadlock in input_inject_event
https://syzkaller.appspot.com/bug?extid=79c403850e6816dc39cf
---
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-08-29 12:52 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=68b1a28f.a00a0220.1337b0.0019.GAE@google.com \
--to=syzbot+listc95489547942700d4b48@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.