From: syzbot <syzbot+liste1602da11e1e5a219c5d@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tj@kernel.org
Subject: [syzbot] Monthly kernfs report (Dec 2024)
Date: Mon, 16 Dec 2024 01:45:24 -0800 [thread overview]
Message-ID: <675ff6b4.050a0220.37aaf.0129.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, 22 issues are still open and 21 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 1094 Yes possible deadlock in __kernfs_remove (2)
https://syzkaller.appspot.com/bug?extid=aa419d82b68e6a7e96c5
<2> 302 Yes WARNING in kernfs_remove_by_name_ns (3)
https://syzkaller.appspot.com/bug?extid=93cbdd0ab421adc5275d
<3> 188 Yes WARNING in kernfs_get (5)
https://syzkaller.appspot.com/bug?extid=2f44671e54488d20f0e6
<4> 73 Yes INFO: task hung in kernfs_dop_revalidate (4)
https://syzkaller.appspot.com/bug?extid=da20d108162166514db6
<5> 56 Yes INFO: task hung in kernfs_add_one
https://syzkaller.appspot.com/bug?extid=e4804edf2708e8b7d2a5
<6> 35 Yes INFO: task hung in do_rmdir (6)
https://syzkaller.appspot.com/bug?extid=4128a26fb0f85ec9e76c
<7> 14 No WARNING in kernfs_new_node (3)
https://syzkaller.appspot.com/bug?extid=306212936b13e520679d
<8> 14 Yes possible deadlock in kernfs_seq_start
https://syzkaller.appspot.com/bug?extid=4c493dcd5a68168a94b2
<9> 11 No possible deadlock in kernfs_fop_write_iter (2)
https://syzkaller.appspot.com/bug?extid=1cfd86253864f61b533e
<10> 2 Yes general protection fault in kernfs_dop_revalidate
https://syzkaller.appspot.com/bug?extid=e37a1730d63d207fe403
---
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:[~2024-12-16 9:45 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=675ff6b4.050a0220.37aaf.0129.GAE@google.com \
--to=syzbot+liste1602da11e1e5a219c5d@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