public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Wangnan (F)" <wangnan0@huawei.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: <acme@kernel.org>, <lizefan@huawei.com>, <pi3orama@163.com>,
	<linux-kernel@vger.kernel.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH] perf hists browser: Fix segfault if use symbol filter in cmdline
Date: Thu, 3 Dec 2015 10:19:36 +0800	[thread overview]
Message-ID: <565FA6B8.7010501@huawei.com> (raw)
In-Reply-To: <20151202154942.GA27992@danjae.kornet>



On 2015/12/2 23:49, Namhyung Kim wrote:
> Hi,
>
> On Wed, Dec 02, 2015 at 11:28:52AM +0000, Wang Nan wrote:
>> If feed perf a symbol filter in cmdline and the result is empty,
>> pressing 'Enter' in the hist browser causes crash:
>>
>>   # ./perf report perf.data   <-- Common mistake for beginners
>>
>> Then press 'Enter':
>>
>>   perf: Segmentation fault
>>   -------- backtrace --------
>>   /home/wangnan/perf[0x53e578]
>>   /lib64/libc.so.6(+0x3545f)[0x7f76bafe045f]
>>   /home/wangnan/perf[0x539dd4]
>>   /home/wangnan/perf(perf_evlist__tui_browse_hists+0x96)[0x53d216]
>>   /home/wangnan/perf(cmd_report+0x1b9f)[0x442c7f]
>>   /home/wangnan/perf[0x47efa2]
>>   /home/wangnan/perf(main+0x5f5)[0x432fa5]
>>   /lib64/libc.so.6(__libc_start_main+0xf4)[0x7f76bafccbd4]
>>   /home/wangnan/perf[0x4330d4]
>>
>> This is because 'perf.data' is interperted as a symbol filter, and the
>> result is empty, so selection is empty. However,
>> hist_browser__toggle_fold() forgets to check it.
>>
>> This patch simply return faluse when selection is NULL.
> s/faluse/false/
>
>> Signed-off-by: Wang Nan <wangnan0@huawei.com>
>> Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> Acked-by: Namhyung Kim <namhyung@kernel.org>
>
> One nitpick below..
>
>> ---
>>   tools/perf/ui/browsers/hists.c | 5 ++++-
>>   1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/tools/perf/ui/browsers/hists.c b/tools/perf/ui/browsers/hists.c
>> index dcdcbaf..33da341 100644
>> --- a/tools/perf/ui/browsers/hists.c
>> +++ b/tools/perf/ui/browsers/hists.c
>> @@ -337,9 +337,12 @@ static bool hist_browser__toggle_fold(struct hist_browser *browser)
>>   {
>>   	struct hist_entry *he = browser->he_selection;
>>   	struct map_symbol *ms = browser->selection;
>> -	struct callchain_list *cl = container_of(ms, struct callchain_list, ms);
>> +	struct callchain_list *cl = ms ? container_of(ms, struct callchain_list, ms) : NULL;
> I think this line is not needed as container_of doesn't make a pointer
> dereference by itself.  Just checking below is enough IMHO.

I know it. Add it only for correctness.

Will be removed.

Thank you.

> Thanks,
> Namhyung
>
>
>>   	bool has_children;
>>   
>> +	if (!ms)
>> +		return false;
>> +
>>   	if (ms == &he->ms)
>>   		has_children = hist_entry__toggle_fold(he);
>>   	else
>> -- 
>> 1.8.3.4
>>



  reply	other threads:[~2015-12-03  2:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 11:28 [PATCH] perf hists browser: Fix segfault if use symbol filter in cmdline Wang Nan
2015-12-02 15:49 ` Namhyung Kim
2015-12-03  2:19   ` Wangnan (F) [this message]
2015-12-06 18:24   ` Arnaldo Carvalho de Melo

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=565FA6B8.7010501@huawei.com \
    --to=wangnan0@huawei.com \
    --cc=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=namhyung@kernel.org \
    --cc=pi3orama@163.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