Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Reply-To: mricon@kernel.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
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
Message-ID: <20230330-b217267c1-e341c3e6314b@bugzilla.kernel.org>
In-Reply-To: <20230330-b217267c0-15b9c837ad2e@bugzilla.kernel.org>
References: <20230330-b217267c0-15b9c837ad2e@bugzilla.kernel.org>
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)
Precedence: bulk

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)