From: syzbot <syzbot+list97c89c631358cb2020f2@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tj@kernel.org
Subject: [syzbot] Monthly kernfs report (Oct 2026)
Date: Fri, 02 Oct 2026 13:33:33 -0700 [thread overview]
Message-ID: <6ac0151d.34119e79.2f92f3.0005.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, 25 issues are still open and 31 have already been fixed.
There are also 11 low-priority issues.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3207 No possible deadlock in kernfs_remove_by_name_ns (2)
https://syzkaller.appspot.com/bug?extid=b50eba6bf6cd3f8ba7d0
<2> 2048 Yes possible deadlock in kernfs_remove
https://syzkaller.appspot.com/bug?extid=2d7d0fbb5fb979113ff3
<3> 241 No possible deadlock in kernfs_fop_readdir
https://syzkaller.appspot.com/bug?extid=8fd10d8928ed1f715290
<4> 32 No possible deadlock in kernfs_add_one
https://syzkaller.appspot.com/bug?extid=f50d605480fdec503770
<5> 18 Yes INFO: rcu detected stall in kernfs_fop_open (7)
https://syzkaller.appspot.com/bug?extid=19d01f6082ec61dd45b2
<6> 676 Yes WARNING in kernfs_remove_by_name_ns (3)
https://syzkaller.appspot.com/bug?extid=93cbdd0ab421adc5275d
<7> 182 Yes INFO: task hung in fdget_pos
https://syzkaller.appspot.com/bug?extid=0ee1ef35cf7e70ce55d7
<8> 64 Yes INFO: rcu detected stall in sys_readlink (5)
https://syzkaller.appspot.com/bug?extid=23e14ec82f3c8692eaa9
<9> 2 Yes INFO: rcu detected stall in kernfs_fop_release (3)
https://syzkaller.appspot.com/bug?extid=087d9dac1f398074ca9f
---
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-10-02 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=6ac0151d.34119e79.2f92f3.0005.GAE@google.com \
--to=syzbot+list97c89c631358cb2020f2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®