From: syzbot <syzbot+list18a75a435a40d93e3954@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tj@kernel.org
Subject: [syzbot] Monthly kernfs report (Aug 2025)
Date: Sat, 23 Aug 2025 09:32:29 -0700 [thread overview]
Message-ID: <68a9ed1d.a00a0220.3557d1.0020.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, 3 new issues were detected and 0 were fixed.
In total, 26 issues are still open and 24 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 869 Yes possible deadlock in kernfs_iop_getattr
https://syzkaller.appspot.com/bug?extid=4bb2305559463e8f6a2a
<2> 450 Yes WARNING in kernfs_remove_by_name_ns (3)
https://syzkaller.appspot.com/bug?extid=93cbdd0ab421adc5275d
<3> 445 Yes WARNING in kernfs_get (5)
https://syzkaller.appspot.com/bug?extid=2f44671e54488d20f0e6
<4> 355 No possible deadlock in lookup_slow (3)
https://syzkaller.appspot.com/bug?extid=65459fd3b61877d717a3
<5> 108 Yes INFO: task hung in fdget_pos
https://syzkaller.appspot.com/bug?extid=0ee1ef35cf7e70ce55d7
<6> 69 Yes INFO: task hung in kernfs_add_one
https://syzkaller.appspot.com/bug?extid=e4804edf2708e8b7d2a5
<7> 64 Yes possible deadlock in kernfs_remove
https://syzkaller.appspot.com/bug?extid=2d7d0fbb5fb979113ff3
<8> 53 Yes INFO: rcu detected stall in sys_unshare (9)
https://syzkaller.appspot.com/bug?extid=872bccd9a68c6ba47718
<9> 43 No INFO: task hung in sb_start_write (2)
https://syzkaller.appspot.com/bug?extid=b3fba2e269970207b61d
<10> 11 No BUG: unable to handle kernel paging request in kernfs_remove_by_name_ns
https://syzkaller.appspot.com/bug?extid=4faa3fd832279bd35a81
---
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-23 16:32 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=68a9ed1d.a00a0220.3557d1.0020.GAE@google.com \
--to=syzbot+list18a75a435a40d93e3954@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.