From: Peter Zijlstra <peterz@infradead.org>
To: Ravi Bangoria <ravi.bangoria@amd.com>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@redhat.com>,
linux-perf-users@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
regressions@lists.linux.dev, lkft-triage@lists.linaro.org,
Stephane Eranian <eranian@google.com>,
Sandipan Das <sandipan.das@amd.com>
Subject: Re: Perf: BUG: kernel NULL pointer dereference, address: 0000000000000198
Date: Thu, 3 Nov 2022 13:33:28 +0100 [thread overview]
Message-ID: <Y2O1GDRrJqIu17vM@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <cb40c209-9c4c-f645-8454-bcd74cb72405@amd.com>
On Thu, Nov 03, 2022 at 05:15:30PM +0530, Ravi Bangoria wrote:
> Sorry was distracted a bit. So, this seems to be happening because of
> race between amd_pmu_enable_all() and perf event NMI. Something like:
>
> amd_pmu_enable_all()
> {
> if (!test_bit(idx, cpuc->active_mask))
>
> --->/* perf NMI entry */
> ...
> x86_pmu_stop() {
> __clear_bit(hwc->idx, cpuc->active_mask);
> cpuc->events[hwc->idx] = NULL;
> }
> ...
> <---/* perf NMI exit */
>
> amd_pmu_enable_event(cpuc->events[idx]);
> }
Hmm, do you have more information? Something like that would require
calling amd_pmu_enable_all() while it is already active -- and that
seems suspect at first glance.
That is, you shouldn't be getting an NMI for @idx before
amd_pmu_enable_event().
next prev parent reply other threads:[~2022-11-03 12:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 6:54 Naresh Kamboju
2022-10-25 4:29 ` Ravi Bangoria
2022-10-25 13:06 ` Ravi Bangoria
2022-10-26 10:05 ` Ravi Bangoria
2022-11-03 11:45 ` Ravi Bangoria
2022-11-03 12:33 ` Peter Zijlstra [this message]
2022-11-03 16:12 ` Ravi Bangoria
2022-11-07 10:29 ` Ravi Bangoria
2022-11-14 4:40 ` [PATCH] perf/x86/amd: Fix crash due to race between amd_pmu_enable_all, perf NMI and throttling Ravi Bangoria
2022-11-16 9:21 ` [tip: perf/urgent] " tip-bot2 for Ravi Bangoria
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=Y2O1GDRrJqIu17vM@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=bp@alien8.de \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mingo@redhat.com \
--cc=naresh.kamboju@linaro.org \
--cc=ravi.bangoria@amd.com \
--cc=regressions@lists.linux.dev \
--cc=sandipan.das@amd.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
all inboxes | Powered by JetHome®