From: Pengfei Xu <pengfei.xu@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Namhyung Kim <namhyung@kernel.org>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
<kan.liang@linux.intel.com>, <linux-kernel@vger.kernel.org>,
<linux-tip-commits@vger.kernel.org>,
<syzkaller-bugs@googlegroups.com>, <x86@kernel.org>,
<lkft-triage@lists.linaro.org>, <dan.carpenter@linaro.org>,
<anders.roxell@linaro.org>, <arnd@arndb.de>,
Linux Kernel Functional Testing <lkft@linaro.org>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>
Subject: Re: [tip: perf/core] perf: Fix event_function_call() locking
Date: Wed, 14 Aug 2024 10:35:52 +0800 [thread overview]
Message-ID: <ZrwYCBazVKjBni/+@xpf.sh.intel.com> (raw)
In-Reply-To: <20240813210209.GA35275@noisy.programming.kicks-ass.net>
Hi Peter and Kim,
I tested this patch on top of 6.11.0-rc3-next-20240812.
This issue can not be reproduced in syzkaller reproducer.
Best Regards,
Thanks!
On 2024-08-13 at 23:02:09 +0200, Peter Zijlstra wrote:
> On Tue, Aug 13, 2024 at 11:28:54AM -0700, Namhyung Kim wrote:
>
> Duh, yeah.
>
> > ---
> > diff --git a/kernel/events/core.c b/kernel/events/core.c
> > index 9893ba5e98aa..85204c2376fa 100644
> > --- a/kernel/events/core.c
> > +++ b/kernel/events/core.c
> > @@ -298,13 +298,14 @@ static int event_function(void *info)
> > static void event_function_call(struct perf_event *event, event_f func, void *data)
> > {
> > struct perf_event_context *ctx = event->ctx;
> > - struct perf_cpu_context *cpuctx = this_cpu_ptr(&perf_cpu_context);
> > + struct perf_cpu_context *cpuctx;
> > struct task_struct *task = READ_ONCE(ctx->task); /* verified in event_function */
> > struct event_function_struct efs = {
> > .event = event,
> > .func = func,
> > .data = data,
> > };
> > + unsigned long flags;
> >
> > if (!event->parent) {
> > /*
> > @@ -327,22 +328,27 @@ static void event_function_call(struct perf_event *event, event_f func, void *da
> > if (!task_function_call(task, event_function, &efs))
> > return;
> >
> > + local_irq_save(flags);
>
> This can just be local_irq_disable() though, seeing how the fingered
> commit replaced raw_spin_lock_irq().
>
> I'll queue the below...
>
> ---
> Subject: perf: Really fix event_function_call() locking
> From: Namhyung Kim <namhyung@kernel.org>
> Date: Tue Aug 13 22:55:11 CEST 2024
>
> Commit 558abc7e3f89 ("perf: Fix event_function_call() locking") lost
> IRQ disabling by mistake.
>
> Fixes: 558abc7e3f89 ("perf: Fix event_function_call() locking")
> Reported-by: Pengfei Xu <pengfei.xu@intel.com>
> Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
> kernel/events/core.c | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -298,8 +298,8 @@ static int event_function(void *info)
> static void event_function_call(struct perf_event *event, event_f func, void *data)
> {
> struct perf_event_context *ctx = event->ctx;
> - struct perf_cpu_context *cpuctx = this_cpu_ptr(&perf_cpu_context);
> struct task_struct *task = READ_ONCE(ctx->task); /* verified in event_function */
> + struct perf_cpu_context *cpuctx;
> struct event_function_struct efs = {
> .event = event,
> .func = func,
> @@ -327,22 +327,25 @@ static void event_function_call(struct p
> if (!task_function_call(task, event_function, &efs))
> return;
>
> + local_irq_disable();
> + cpuctx = this_cpu_ptr(&perf_cpu_context);
> perf_ctx_lock(cpuctx, ctx);
> /*
> * Reload the task pointer, it might have been changed by
> * a concurrent perf_event_context_sched_out().
> */
> task = ctx->task;
> - if (task == TASK_TOMBSTONE) {
> - perf_ctx_unlock(cpuctx, ctx);
> - return;
> - }
> + if (task == TASK_TOMBSTONE)
> + goto unlock;
> if (ctx->is_active) {
> perf_ctx_unlock(cpuctx, ctx);
> + local_irq_enable();
> goto again;
> }
> func(event, NULL, ctx, data);
> +unlock:
> perf_ctx_unlock(cpuctx, ctx);
> + local_irq_enable();
> }
>
> /*
next prev parent reply other threads:[~2024-08-14 2:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 11:29 [PATCH 0/5] perf: Per PMU context reschedule and misc Peter Zijlstra
2024-08-07 11:29 ` [PATCH 1/5] perf: Optimize context reschedule for single PMU cases Peter Zijlstra
2024-08-08 10:32 ` [tip: perf/core] " tip-bot2 for Peter Zijlstra
2024-08-07 11:29 ` [PATCH 2/5] perf: Extract a few helpers Peter Zijlstra
2024-08-08 10:32 ` [tip: perf/core] " tip-bot2 for Peter Zijlstra
2024-08-07 11:29 ` [PATCH 3/5] perf: Fix event_function_call() locking Peter Zijlstra
2024-08-08 10:32 ` [tip: perf/core] " tip-bot2 for Peter Zijlstra
2024-08-13 1:34 ` Pengfei Xu
2024-08-13 15:19 ` Naresh Kamboju
2024-08-13 18:28 ` Namhyung Kim
2024-08-13 21:02 ` Peter Zijlstra
2024-08-14 2:35 ` Pengfei Xu [this message]
2024-08-07 11:29 ` [PATCH 4/5] perf: Add context time freeze Peter Zijlstra
2024-08-07 15:17 ` Liang, Kan
2024-08-07 19:09 ` Peter Zijlstra
2024-08-08 10:32 ` [tip: perf/core] " tip-bot2 for Peter Zijlstra
2024-08-07 11:29 ` [PATCH 5/5] perf: Optimize __pmu_ctx_sched_out() Peter Zijlstra
2024-08-08 10:32 ` [tip: perf/core] " tip-bot2 for Peter Zijlstra
2024-08-07 15:19 ` [PATCH 0/5] perf: Per PMU context reschedule and misc Liang, Kan
2024-08-07 18:54 ` Namhyung Kim
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=ZrwYCBazVKjBni/+@xpf.sh.intel.com \
--to=pengfei.xu@intel.com \
--cc=anders.roxell@linaro.org \
--cc=andrii.nakryiko@gmail.com \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=lkft@linaro.org \
--cc=namhyung@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=x86@kernel.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