From: Frederic Weisbecker <frederic@kernel.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.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>,
"Liang, Kan" <kan.liang@linux.intel.com>,
Oleg Nesterov <oleg@redhat.com>, Yi Lai <yi1.lai@linux.intel.com>,
syzbot+3c4321e10eea460eb606@syzkaller.appspotmail.com
Subject: Re: [PATCH] perf: Fix hang while freeing sigtrap event
Date: Wed, 5 Mar 2025 15:56:22 +0100 [thread overview]
Message-ID: <Z8hmFhg5g7n3JKXP@localhost.localdomain> (raw)
In-Reply-To: <20250305081907.xHiR7jy0@linutronix.de>
Le Wed, Mar 05, 2025 at 09:19:07AM +0100, Sebastian Andrzej Siewior a écrit :
> On 2025-03-04 14:54:46 [+0100], Frederic Weisbecker wrote:
> > Perf can hang while freeing a sigtrap event if a related deferred
> > signal hadn't managed to be sent before the file got closed:
> …
> > Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
>
> Reviewed-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
>
> Both of the test cases pass… This looks way simpler than the initial
> attempts, why didn't we go with this initially?
Because I was afraid that a pending perf signal queued before or during
exec may be delivered later to an suid process. But eventually I don't see
anything that prevented from that even before this patch.
Thanks.
next prev parent reply other threads:[~2025-03-05 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 13:54 [PATCH] perf: Fix hang while freeing sigtrap event Frederic Weisbecker
2025-03-05 8:19 ` Sebastian Andrzej Siewior
2025-03-05 14:56 ` Frederic Weisbecker [this message]
2025-03-18 8:44 ` Frederic Weisbecker
2025-03-31 19:24 ` Frederic Weisbecker
2025-04-08 12:33 ` Frederic Weisbecker
2025-04-08 19:05 ` [tip: perf/core] " tip-bot2 for Frederic Weisbecker
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=Z8hmFhg5g7n3JKXP@localhost.localdomain \
--to=frederic@kernel.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=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=syzbot+3c4321e10eea460eb606@syzkaller.appspotmail.com \
--cc=yi1.lai@linux.intel.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