From: syzbot <syzbot+list7a9bc4f901342664924c@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tj@kernel.org
Subject: [syzbot] Monthly kernfs report (May 2023)
Date: Fri, 05 May 2023 14:41:41 -0700 [thread overview]
Message-ID: <0000000000009dc8bd05faf927cb@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, 1 new issues were detected and 0 were fixed.
In total, 8 issues are still open and 21 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 95 Yes WARNING in kernfs_remove_by_name_ns (3)
https://syzkaller.appspot.com/bug?extid=93cbdd0ab421adc5275d
<2> 49 Yes inconsistent lock state in find_vmap_area
https://syzkaller.appspot.com/bug?extid=8d19062486784d15dda9
<3> 30 Yes KASAN: use-after-free Read in kernfs_add_one
https://syzkaller.appspot.com/bug?extid=ef17b5b364116518fd65
<4> 1 No KASAN: slab-use-after-free Read in kernfs_xattr_get
https://syzkaller.appspot.com/bug?extid=1b11da2ef24dccc2e98d
---
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:[~2023-05-05 21:43 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=0000000000009dc8bd05faf927cb@google.com \
--to=syzbot+list7a9bc4f901342664924c@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).