From: Peter Zijlstra <peterz@infradead.org>
To: Liangyan <liangyan.peng@bytedance.com>
Cc: mingo@redhat.com, acme@kernel.org, namhyung@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
james.clark@linaro.org, bigeasy@linutronix.de,
zengxianjun@bytedance.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf/core: Fix pending work re-queued in __perf_event_overflow
Date: Sun, 9 Nov 2025 12:45:00 +0100 [thread overview]
Message-ID: <20251109114500.GC2545891@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20251109103253.57081-1-liangyan.peng@bytedance.com>
On Sun, Nov 09, 2025 at 06:32:53PM +0800, Liangyan wrote:
> A race condition occurs between task context and IRQ context when
> handling sigtrap tracepoint event overflows:
>
> 1. In task context, an event is overflowed and its pending work is
> queued to task->task_works
> 2. Before pending_work is set, the same event overflows in IRQ context
> 3. Both contexts queue the same perf pending work to task->task_works
>
> This double queuing causes:
> - task_work_run() enters infinite loop calling perf_pending_task()
> - Potential warnings and use-after-free when event is freed in
> perf_pending_task()
>
> Fix the race by disabling interrupts during queuing of perf pending work.
> Fixes: c5d93d23a260 ("perf: Enqueue SIGTRAP always via task_work.")
> Reported-by: Xianjun Zeng <zengxianjun@bytedance.com>
> Signed-off-by: Liangyan <liangyan.peng@bytedance.com>
> ---
> kernel/events/core.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index cae921f4d137..6c35a129f185 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -10427,12 +10427,14 @@ static int __perf_event_overflow(struct perf_event *event,
> bool valid_sample = sample_is_allowed(event, regs);
> unsigned int pending_id = 1;
> enum task_work_notify_mode notify_mode;
> + unsigned long flags;
>
> if (regs)
> pending_id = hash32_ptr((void *)instruction_pointer(regs)) ?: 1;
>
> notify_mode = in_nmi() ? TWA_NMI_CURRENT : TWA_RESUME;
>
> + local_irq_save(flags);
This could be written as:
/*
* Comment that explains why we need to disable IRQs.
*/
guard(irqsave)();
> if (!event->pending_work &&
> !task_work_add(current, &event->pending_task, notify_mode)) {
> event->pending_work = pending_id;
> @@ -10458,6 +10460,7 @@ static int __perf_event_overflow(struct perf_event *event,
> */
> WARN_ON_ONCE(event->pending_work != pending_id);
> }
> + local_irq_restore(flags);
> }
>
> READ_ONCE(event->overflow_handler)(event, data, regs);
> --
> 2.39.3 (Apple Git-145)
>
next prev parent reply other threads:[~2025-11-09 11:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 10:32 Liangyan
2025-11-09 11:45 ` Peter Zijlstra [this message]
2025-11-09 16:41 ` [PATCH v2] " Liangyan
2025-11-11 13:30 ` Sebastian Andrzej Siewior
2025-11-12 3:28 ` [External] " Liangyan
2025-11-14 3:33 ` [PATCH v3] " Liangyan
2025-11-14 8:02 ` Sebastian Andrzej Siewior
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=20251109114500.GC2545891@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=liangyan.peng@bytedance.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=zengxianjun@bytedance.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®