From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Tengda Wu <wutengda@huaweicloud.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] perf/core: Prevent duplicate sigtrap task work enqueue
Date: Mon, 16 Nov 2026 10:47:06 +0100 [thread overview]
Message-ID: <20261116094706.GX5vD02a@linutronix.de> (raw)
In-Reply-To: <ff842e802e9ecb74510a90964f8ad2c4825834b7.1793870900.git.wutengda@huaweicloud.com>
On 2026-11-05 09:30:43 [+0000], Tengda Wu wrote:
> The sigtrap handling in __perf_event_overflow() checks
> event->pending_work before calling task_work_add(), but only sets
> pending_work after the task work has been queued.
>
> This leaves a window where an NMI can interrupt task_work_add()
> and re-enter __perf_event_overflow() for the same event. Since
> pending_work is still zero, the nested invocation can enqueue
> the same pending_task again.
>
> The re-entrant call path is:
>
> __perf_event_overflow()
> task_work_add()
> kasan_record_aux_stack()
> <NMI>
> __perf_event_overflow()
> task_work_add()
>
> The nested invocation can enqueue pending_task before the
> outer invocation does. When the outer invocation resumes, it
> inserts the same task_work entry again, potentially creating
> a cycle in the task work list.
>
> This causes perf_pending_task() to be executed repeatedly
> and leads to unbalanced event reference counting.
>
> Use cmpxchg() to atomically claim pending_work before calling
> task_work_add(). This ensures that only one invocation can
> enqueue the pending_task, even when interrupted by an NMI.
>
> If task_work_add() fails, clear the pending_work claim so that
> a subsequent overflow can retry.
>
> Also use READ_ONCE() when checking pending_work in the
> exclude_kernel warning path to avoid an unsynchronized read.
>
> Fixes: c5d93d23a260 ("perf: Enqueue SIGTRAP always via task_work.")
> Signed-off-by: Tengda Wu <wutengda@huaweicloud.com>
> ---
> kernel/events/core.c | 23 ++++++++++++-----------
> 1 file changed, 12 insertions(+), 11 deletions(-)
>
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index 457d75ea7142..ee5c59158b89 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -10925,16 +10925,17 @@ static int __perf_event_overflow(struct perf_event *event,
>
> notify_mode = in_nmi() ? TWA_NMI_CURRENT : TWA_RESUME;
>
> - if (!event->pending_work &&
> - !task_work_add(current, &event->pending_task, notify_mode)) {
> - event->pending_work = pending_id;
> - local_inc(&event->ctx->nr_no_switch_fast);
> - WARN_ON_ONCE(!atomic_long_inc_not_zero(&event->refcount));
> -
> - event->pending_addr = 0;
> - if (valid_sample && (data->sample_flags & PERF_SAMPLE_ADDR))
> - event->pending_addr = data->addr;
> -
> + if (cmpxchg(&event->pending_work, 0, pending_id) == 0) {
would cmpxchg_acquire() here make sense?
> + if (!task_work_add(current, &event->pending_task, notify_mode)) {
> + local_inc(&event->ctx->nr_no_switch_fast);
> + WARN_ON_ONCE(!atomic_long_inc_not_zero(&event->refcount));
> +
> + event->pending_addr = 0;
> + if (valid_sample && (data->sample_flags & PERF_SAMPLE_ADDR))
> + event->pending_addr = data->addr;
> + } else {
> + cmpxchg(&event->pending_work, pending_id, 0);
if the task_work_add() fails then smp_store_release(, 0) since only the
executed task_work can release it back to 0. The cmpxchg seems not
needed.
> + }
> } else if (event->attr.exclude_kernel && valid_sample) {
> /*
> * Should not be able to return to user space without
> @@ -10948,7 +10949,7 @@ static int __perf_event_overflow(struct perf_event *event,
> * To approximate progress (with false negatives),
> * check 32-bit hash of the current IP.
> */
> - WARN_ON_ONCE(event->pending_work != pending_id);
> + WARN_ON_ONCE(READ_ONCE(event->pending_work) != pending_id);
smp_load_acquire()
perf_pending_task() could maybe get a xchg_release(, 0). This however is
wrong because it would reset perf_event::pending_work and make it
available for __perf_event_overflow() again. I think it should have a
load_acquire() first, and have the store_release() after perf_sigtrap().
Comments?
> }
> }
>
Sebastian
next prev parent reply other threads:[~2026-11-16 9:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 9:30 [PATCH v3 0/2] perf/core: Fix sigtrap task_work races Tengda Wu
2026-11-05 9:30 ` [PATCH v3 1/2] perf/core: Prevent duplicate sigtrap task work enqueue Tengda Wu
2026-11-16 9:47 ` Sebastian Andrzej Siewior [this message]
2026-11-05 9:30 ` [PATCH v3 2/2] perf/core: Disable context fast-swap for sigtrap events Tengda Wu
2026-11-16 10:17 ` Sebastian Andrzej Siewior
2026-11-05 9:43 ` [PATCH v3 0/2] perf/core: Fix sigtrap task_work races Tengda Wu
2026-11-05 9:47 ` Tengda Wu
2026-11-16 6:12 ` Tengda Wu
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=20261116094706.GX5vD02a@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--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=peterz@infradead.org \
--cc=wutengda@huaweicloud.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®