From: Danishk2445 <danishkhateeb03@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Danish Khateeb <danishkhateeb03@gmail.com>,
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>,
Marco Elver <elver@google.com>,
Frederic Weisbecker <frederic@kernel.org>,
Luo Gengkun <luogengkun2@huawei.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] perf/core: Don't send SIGTRAP after exec removed the event
Date: Wed, 30 Sep 2026 10:59:00 -0500 [thread overview]
Message-ID: <20260930155900.65984-1-danishkhateeb03@gmail.com> (raw)
In-Reply-To: <20260930151610.GN88198@noisy.programming.kicks-ass.net>
From: Danish Khateeb <danishkhateeb03@gmail.com>
On Wed, Sep 30, 2026 at 05:16:10PM +0200, Peter Zijlstra wrote:
> Is this the same problem as this one?
>
> https://patch.msgid.link/20260920075026.990582-1-luogengkun2@huawei.com
No. That one is an exec into a non-dumpable binary, where
perf_event_exit_task() sets TASK_TOMBSTONE and the WARN fires. This is
an ordinary exec: ctx->task doesn't change and the SIGTRAP kills the
new program. With Luo's patch on rc5 that still happens (567 of 2000
runs), with this one it doesn't, and Luo's WARN goes away too, since
perf_event_exit_task() sets every event to PERF_EVENT_STATE_EXIT.
Thanks
Danish
prev parent reply other threads:[~2026-09-30 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 14:42 Danish Khateeb
2026-09-30 15:16 ` Peter Zijlstra
2026-09-30 15:59 ` Danishk2445 [this message]
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=20260930155900.65984-1-danishkhateeb03@gmail.com \
--to=danishkhateeb03@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=elver@google.com \
--cc=frederic@kernel.org \
--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=luogengkun2@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=stable@vger.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
all inboxes | Powered by JetHome®