From: Namhyung Kim <namhyung@kernel.org>
To: Wang Nan <wangnan0@huawei.com>
Cc: acme@kernel.org, lizefan@huawei.com,
linux-kernel@vger.kernel.org, pi3orama@163.com
Subject: Re: [PATCH] perf tools: Fix segfault in 'perf top'
Date: Sat, 12 Sep 2015 01:22:07 +0900 [thread overview]
Message-ID: <20150911162207.GD3447@danjae.kornet> (raw)
In-Reply-To: <1441947551-48992-1-git-send-email-wangnan0@huawei.com>
On Fri, Sep 11, 2015 at 04:59:11AM +0000, Wang Nan wrote:
> 'perf top' segfaults with following operation:
>
> # perf top -e page-faults -p 15173 # 15173 never generate page-fault
>
> Then on the resulting empty interface, press right key:
>
> # ./perf top -e page-faults -p 11400
> perf: Segmentation fault
> -------- backtrace --------
> ./perf[0x535428]
> /lib64/libc.so.6(+0x3545f)[0x7f0dd360745f]
> ./perf[0x531d46]
> ./perf(perf_evlist__tui_browse_hists+0x96)[0x5340d6]
> ./perf[0x44ba2f]
> /lib64/libpthread.so.0(+0x81d0)[0x7f0dd49dc1d0]
> /lib64/libc.so.6(clone+0x6c)[0x7f0dd36b90dc]
>
> The bug reside in perf_evsel__hists_browse() that, in the above circumstance
> browser->selection can be NULL, but code after skip_annotation doesn't consider
> it.
>
> This patch fix it by checing browser->selection before fetching
> browser->selection->map and browser->selection->sym.
I'm ok with this change, just a nitpick below..
>
> Signed-off-by: Wang Nan <wangnan0@huawei.com>
> Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
> Cc: Namhyung Kim <namhyung@kernel.org>
> ---
> tools/perf/ui/browsers/hists.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/ui/browsers/hists.c b/tools/perf/ui/browsers/hists.c
> index e4fd40f..b00fa92 100644
> --- a/tools/perf/ui/browsers/hists.c
> +++ b/tools/perf/ui/browsers/hists.c
> @@ -2017,7 +2017,8 @@ skip_annotation:
> &options[nr_options], dso);
> nr_options += add_map_opt(browser, &actions[nr_options],
> &options[nr_options],
> - browser->selection->map);
> + browser->selection ?
> + browser->selection->map : NULL);
> nr_options += add_socket_opt(browser, &actions[nr_options],
> &options[nr_options],
> socket);
> @@ -2030,7 +2031,10 @@ skip_annotation:
> nr_options += add_script_opt(browser,
> &actions[nr_options],
> &options[nr_options],
> - NULL, browser->selection->sym);
> + NULL,
> + browser->selection ?
> + browser->selection->sym :
> + NULL);
Is this really needed? IIUC browser->selection is not NULL if
browser->he_selection is not NULL. Did you see a case it's NULL?
Also passing a NULL thread and a NULL sym is meaningless here since
it's a duplication..
Thanks,
Namhyung
> }
> nr_options += add_script_opt(browser, &actions[nr_options],
> &options[nr_options], NULL, NULL);
> --
> 1.8.3.4
>
next prev parent reply other threads:[~2015-09-11 16:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 4:59 Wang Nan
2015-09-11 16:22 ` Namhyung Kim [this message]
2015-09-14 10:15 ` Wangnan (F)
2015-09-14 10:23 ` [PATCH v2] " Wang Nan
2015-09-14 18:07 ` Arnaldo Carvalho de Melo
2015-09-14 18:12 ` Arnaldo Carvalho de Melo
2015-09-16 7:27 ` [tip:perf/core] perf top: Fix segfault pressing -> with no hist entries tip-bot for Wang Nan
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=20150911162207.GD3447@danjae.kornet \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=pi3orama@163.com \
--cc=wangnan0@huawei.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®