From: sashiko-bot@kernel.org
To: "Puranjay Mohan" <puranjay@kernel.org>
Cc: linux-perf-users@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v7 1/3] perf/core: Fix NULL pmu_ctx passed to pmu->sched_task()
Date: Mon, 10 Aug 2026 14:03:05 +0000 [thread overview]
Message-ID: <20260810140306.C1D721F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260810133540.1947118-2-puranjay@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] Per-CPU PMUs missing `sched_task` callbacks during context switches if a task context exists.
--
--- Patch [1]: [PATCH v7 1/3] perf/core: Fix NULL pmu_ctx passed to pmu->sched_task() ---
commit 333df3e02c2d6b54e5bd528f91779820677d118e
Author: Puranjay Mohan <puranjay@kernel.org>
perf/core: Fix NULL pmu_ctx passed to pmu->sched_task()
perf_pmu_sched_task() returns early when cpuctx->task_ctx is set, and
cpc->task_epc is only non-NULL while a task context is scheduled in on
this CPU. This patch passes &cpc->epc instead, which is the CPU-wide
context for this PMU, avoiding a NULL pointer dereference.
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index ba5bd6a78fe7b..c372213ffc883 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -3907,7 +3907,7 @@ static void __perf_pmu_sched_task(struct perf_cpu_pmu_context *cpc,
> perf_ctx_lock(cpuctx, cpuctx->task_ctx);
> perf_pmu_disable(pmu);
>
> - pmu->sched_task(cpc->task_epc, task, sched_in);
> + pmu->sched_task(&cpc->epc, task, sched_in);
[Severity: High]
This isn't a bug introduced by this patch, but does the early return in
perf_pmu_sched_task() skip callbacks for CPU-wide PMUs?
If a system-wide PMU event is active (sched_cb_usage > 0), and a context
switch occurs to or from a task with an active perf event (meaning
cpuctx->task_ctx is set), perf_pmu_sched_task() returns early:
kernel/events/core.c:perf_pmu_sched_task() {
...
/* cpuctx->task_ctx will be handled in perf_event_context_sched_in/out */
if (prev == next || cpuctx->task_ctx)
return;
...
}
It seems to rely on perf_event_context_sched_out/in() to handle the
callbacks. However, perf_ctx_sched_task_cb() only iterates over the task's
pmu_ctx_list:
kernel/events/core.c:perf_ctx_sched_task_cb() {
...
list_for_each_entry(pmu_ctx, &ctx->pmu_ctx_list, pmu_ctx_entry) {
cpc = this_cpc(pmu_ctx->pmu);
if (cpc->sched_cb_usage && pmu_ctx->pmu->sched_task)
pmu_ctx->pmu->sched_task(pmu_ctx, task, sched_in);
}
...
}
If the task's perf event is for a different PMU (like a software event), the
CPU-wide PMU won't be in ctx->pmu_ctx_list. Does this mean the CPU-wide
PMU's sched_task() callback is completely skipped during the context switch,
potentially corrupting hardware tracing or leaking branch records across tasks?
>
> perf_pmu_enable(pmu);
> perf_ctx_unlock(cpuctx, cpuctx->task_ctx);
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260810133540.1947118-1-puranjay@kernel.org?part=1
next prev parent reply other threads:[~2026-08-10 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 13:35 [PATCH v7 0/3] perf/core: sched_task() dispatch and branch entry fixes Puranjay Mohan
2026-08-10 13:35 ` [PATCH v7 1/3] perf/core: Fix NULL pmu_ctx passed to pmu->sched_task() Puranjay Mohan
2026-08-10 14:03 ` sashiko-bot [this message]
2026-08-10 14:04 ` Puranjay Mohan
2026-08-10 13:35 ` [PATCH v7 2/3] perf/core: Run sched_task() for PMUs with only CPU-wide events Puranjay Mohan
2026-08-10 13:35 ` [PATCH v7 3/3] perf/core: Fill branch entries with a single assignment Puranjay Mohan
2026-08-10 14:04 ` sashiko-bot
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=20260810140306.C1D721F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=puranjay@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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