From: syzbot <syzbot+list4e6906a01c6f7576013d@syzkaller.appspotmail.com>
To: acme@kernel.org, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org, mingo@redhat.com,
namhyung@kernel.org, peterz@infradead.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly perf report (Sep 2024)
Date: Mon, 02 Sep 2024 01:23:29 -0700 [thread overview]
Message-ID: <000000000000dea27206211ea733@google.com> (raw)
Hello perf maintainers/developers,
This is a 31-day syzbot report for the perf subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/perf
During the period, 2 new issues were detected and 0 were fixed.
In total, 6 issues are still open and 22 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 2373 Yes WARNING: suspicious RCU usage in get_callchain_entry
https://syzkaller.appspot.com/bug?extid=72a43cdb78469f7fbad1
<2> 59 No KASAN: slab-use-after-free Read in uprobe_mmap
https://syzkaller.appspot.com/bug?extid=ab687d3cbad90def4b18
<3> 8 Yes KASAN: slab-use-after-free Read in __uprobe_unregister
https://syzkaller.appspot.com/bug?extid=f7a1c2c2711e4a780f19
<4> 6 No KCSAN: data-race in _free_event / perf_pending_task
https://syzkaller.appspot.com/bug?extid=ef3b1bb7dd78b4e9109c
---
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-09-02 8:23 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=000000000000dea27206211ea733@google.com \
--to=syzbot+list4e6906a01c6f7576013d@syzkaller.appspotmail.com \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
/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