From: "Kernel.org Bugbot" <bugbot@kernel.org>
To: acme@kernel.org, linux-perf-users@vger.kernel.org,
peterz@infradead.org, pengfei.xu@intel.com, bugs@lists.linux.dev,
linux-kernel@vger.kernel.org, mricon@kernel.org,
mingo@redhat.com
Subject: Re: [Syzkaller & bisect] There is "soft lockup in sys_perf_event_open" BUG in v6.3-rc4 kernel
Date: Thu, 30 Mar 2023 21:39:14 +0000 (UTC) [thread overview]
Message-ID: <20230330-b217267c1-e341c3e6314b@bugzilla.kernel.org> (raw)
In-Reply-To: <20230330-b217267c0-15b9c837ad2e@bugzilla.kernel.org>
mricon@kernel.org writes via Kernel.org Bugzilla:
(In reply to xupengfe from comment #0)
> And bisected found that the first bad commit in tip repo was:
> "
> 79df45731da68772d2285265864a52c900b8c65f
> perf/core: Allow ftrace for functions in kernel/event/core.c
> "
Hi, all:
I'm giving this bug report the inaugural bugbot treatment. It will create a new thread and send messages to the maintainers of "PERFORMANCE EVENTS SUBSYSTEM" (based on kernel/events/core.c reported in the bug). If it's not correct, please follow up and suggest a different subsystem that is responsible for this bug.
Best regards,
Konstantin
(You don't need to touch bugzilla to participate in this discussion, you can just reply to messages as if it were any other mailing list thread. It's possible that bugbot has a few bugs of its own, so please be patient and I will fix them as they happen.)
View: https://bugzilla.kernel.org/show_bug.cgi?id=217267#c1
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (peebz 0.1)
next prev parent reply other threads:[~2023-03-30 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 21:39 [Syzkaller & bisect] There is "soft lockup in sys_perf_event_open" BUG in v6.3-rc4 kernel Kernel.org Bugbot
2023-03-30 21:39 ` Kernel.org Bugbot [this message]
2023-03-31 0:59 ` Kernel.org Bugbot
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=20230330-b217267c1-e341c3e6314b@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=acme@kernel.org \
--cc=bugs@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mricon@kernel.org \
--cc=pengfei.xu@intel.com \
--cc=peterz@infradead.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).