[syzbot] Monthly kernfs report (Oct 2025)

[syzbot]

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, 1 new issues were detected and 0 were fixed.
In total, 26 issues are still open and 25 have already been fixed.

Some of the still happening issues:

Ref Crashes Repro Title
<1> 2087 Yes possible deadlock in kernfs_iop_getattr
https://syzkaller.appspot.com/bug?extid=4bb2305559463e8f6a2a
<2> 504 Yes WARNING in kernfs_remove_by_name_ns (3)
https://syzkaller.appspot.com/bug?extid=93cbdd0ab421adc5275d
<3> 500 Yes WARNING in kernfs_get (5)
https://syzkaller.appspot.com/bug?extid=2f44671e54488d20f0e6
<4> 112 Yes INFO: task hung in fdget_pos
https://syzkaller.appspot.com/bug?extid=0ee1ef35cf7e70ce55d7
<5> 78 No possible deadlock in kernfs_fop_write_iter (2)
https://syzkaller.appspot.com/bug?extid=1cfd86253864f61b533e
<6> 65 No possible deadlock in kernfs_fop_readdir
https://syzkaller.appspot.com/bug?extid=8fd10d8928ed1f715290
<7> 59 Yes possible deadlock in walk_component (4)
https://syzkaller.appspot.com/bug?extid=b4567a8b2d2ad5f9dd06
<8> 42 Yes INFO: rcu detected stall in hub_event (2)
https://syzkaller.appspot.com/bug?extid=039eab266c6321a174bd
<9> 30 Yes INFO: task hung in kernfs_remove_by_name_ns (2)
https://syzkaller.appspot.com/bug?extid=6d5664213a6db9a5a72c
<10> 23 Yes possible deadlock in kernfs_seq_start
https://syzkaller.appspot.com/bug?extid=4c493dcd5a68168a94b2

---
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 syzk...@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.