From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Michael Petlan <mpetlan@redhat.com>
Cc: acme@redhat.com, linux-perf-users@vger.kernel.org,
jolsa@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf trace: Fix race in signal handling
Date: Fri, 5 Mar 2021 14:16:24 -0300 [thread overview]
Message-ID: <YEJnaMzH2ctp3PPx@kernel.org> (raw)
In-Reply-To: <20210302144120.17362-1-mpetlan@redhat.com>
Em Tue, Mar 02, 2021 at 03:41:20PM +0100, Michael Petlan escreveu:
> Since a lot of stuff happens before the SIGINT signal handler is registered
> (scanning /proc/*, etc.), on bigger systems, such as Cavium Sabre CN99xx,
> it may happen that first interrupt signal is lost and perf isn't correctly
> terminated.
>
> The reproduction code might look like the following:
>
> perf trace -a &
> PERF_PID=$!
> sleep 4
> kill -INT $PERF_PID
>
> The issue has been found on a CN99xx machine with RHEL-8 and the patch fixes
> it by registering the signal handlers earlier in the init stage.
Thanks, applied.
- Arnaldo
> Suggested-by: Jiri Olsa <jolsa@redhat.com>
> Signed-off-by: Michael Petlan <mpetlan@redhat.com>
> Tested-by: Michael Petlan <mpetlan@redhat.com>
> ---
> tools/perf/builtin-trace.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/tools/perf/builtin-trace.c b/tools/perf/builtin-trace.c
> index 85b6a46e85b6..7ec18ff57fc4 100644
> --- a/tools/perf/builtin-trace.c
> +++ b/tools/perf/builtin-trace.c
> @@ -3964,9 +3964,6 @@ static int trace__run(struct trace *trace, int argc, const char **argv)
>
> evlist__config(evlist, &trace->opts, &callchain_param);
>
> - signal(SIGCHLD, sig_handler);
> - signal(SIGINT, sig_handler);
> -
> if (forks) {
> err = evlist__prepare_workload(evlist, &trace->opts.target, argv, false, NULL);
> if (err < 0) {
> @@ -4827,6 +4824,8 @@ int cmd_trace(int argc, const char **argv)
>
> signal(SIGSEGV, sighandler_dump_stack);
> signal(SIGFPE, sighandler_dump_stack);
> + signal(SIGCHLD, sig_handler);
> + signal(SIGINT, sig_handler);
>
> trace.evlist = evlist__new();
> trace.sctbl = syscalltbl__new();
> --
> 2.18.4
>
--
- Arnaldo
parent reply other threads:[~2021-03-05 17:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210302144120.17362-1-mpetlan@redhat.com>]
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=YEJnaMzH2ctp3PPx@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mpetlan@redhat.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;
as well as URLs for NNTP newsgroup(s).