From: syzbot <syzbot+listbd47593dbaa9c88b91d7@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tj@kernel.org
Subject: [syzbot] Monthly kernfs report (Jul 2025)
Date: Wed, 23 Jul 2025 03:04:25 -0700 [thread overview]
Message-ID: <6880b3a9.050a0220.40ccf.0002.GAE@google.com> (raw)
Hello kernfs maintainers/developers,
This is a 31-day syzbot report for the kernfs subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/kernfs
During the period, 0 new issues were detected and 0 were fixed.
In total, 20 issues are still open and 23 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 422 Yes WARNING in kernfs_get (5)
https://syzkaller.appspot.com/bug?extid=2f44671e54488d20f0e6
<2> 422 Yes WARNING in kernfs_remove_by_name_ns (3)
https://syzkaller.appspot.com/bug?extid=93cbdd0ab421adc5275d
<3> 353 No possible deadlock in lookup_slow (3)
https://syzkaller.appspot.com/bug?extid=65459fd3b61877d717a3
<4> 113 Yes INFO: task hung in kernfs_dop_revalidate (4)
https://syzkaller.appspot.com/bug?extid=da20d108162166514db6
<5> 68 No possible deadlock in kernfs_fop_write_iter (2)
https://syzkaller.appspot.com/bug?extid=1cfd86253864f61b533e
<6> 33 Yes WARNING in kernfs_new_node (3)
https://syzkaller.appspot.com/bug?extid=306212936b13e520679d
<7> 32 Yes possible deadlock in walk_component (4)
https://syzkaller.appspot.com/bug?extid=b4567a8b2d2ad5f9dd06
<8> 25 Yes INFO: task hung in kernfs_remove_by_name_ns (2)
https://syzkaller.appspot.com/bug?extid=6d5664213a6db9a5a72c
<9> 22 Yes possible deadlock in kernfs_seq_start
https://syzkaller.appspot.com/bug?extid=4c493dcd5a68168a94b2
<10> 10 Yes INFO: task hung in pipe_write (6)
https://syzkaller.appspot.com/bug?extid=5984e31a805252b3b40a
---
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-07-23 10:04 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=6880b3a9.050a0220.40ccf.0002.GAE@google.com \
--to=syzbot+listbd47593dbaa9c88b91d7@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
/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.