From: "Wangnan (F)" <wangnan0@huawei.com>
To: Tong Zhang <ztong@vt.edu>, <acme@redhat.com>, <jpoimboe@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] broken perf tool on 4.4-rc1
Date: Mon, 1 Feb 2016 11:23:57 +0800 [thread overview]
Message-ID: <56AECFCD.3050708@huawei.com> (raw)
In-Reply-To: <56AEC026.2080509@huawei.com>
On 2016/2/1 10:17, Wangnan (F) wrote:
>
>
> On 2016/1/31 5:02, Tong Zhang wrote:
>> reproduce:
>> lzto@objd ~ $ ~/linux/tools/perf/perf record -I -e
>> intel_pt/tsc=1,noretcomp=1/u /bin/ls
>> lzto@objd ~ $ ~/linux/tools/perf/perf script -F
>> event,comm,pid,tid,time,addr,ip,sym,dso,iregs
>> Segmentation fault
>> lzto@objd ~ $
>>
>> Upon further investigation, it seems that
>> commit 747a9b0a08ae ("Merge branch 'perf-urgent-for-linus' of
>> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip")
>> breaks perf tool.
>>
>> __list_del(): tools/include/linux/list.h does not check null pointer
>> dereference
>
> I don't have a Boradwell system, unable to reproduce the fault.
>
Now I find one. The stack is:
#0 __list_del (next=0x1a12440, prev=0x0) at
/home/w00229757/kernel-hydrogen/tools/include/linux/list.h:89
#1 __list_del_entry (entry=0x1a12440) at
/home/w00229757/kernel-hydrogen/tools/include/linux/list.h:101
#2 list_del_init (entry=0x1a12440) at
/home/w00229757/kernel-hydrogen/tools/include/linux/list.h:144
#3 thread__put (thread=0x1a12440) at util/thread.c:104
#4 0x0000000000502e99 in __thread__zput (thread=0x1a12330) at
util/thread.h:49
#5 intel_pt_process_auxtrace_info (event=<optimized out>,
session=0x19f88d0) at util/intel-pt.c:2156
#6 0x00000000004c75a0 in perf_session__process_user_event
(file_offset=584, event=0x7ffff7fa6248, session=0x19f88d0)
at util/session.c:1353
#7 perf_session__process_event (session=session@entry=0x19f88d0,
event=event@entry=0x7ffff7fa6248,
file_offset=file_offset@entry=584) at util/session.c:1472
#8 0x00000000004c9907 in __perf_session__process_events
(file_size=273984, data_size=<optimized out>,
data_offset=<optimized out>, session=0x19f88d0) at util/session.c:1825
#9 perf_session__process_events (session=0x19f88d0) at util/session.c:1875
#10 0x00000000004554b0 in __cmd_script (script=0x7fffffffd440) at
builtin-script.c:1049
#11 cmd_script (argc=<optimized out>, argv=<optimized out>,
prefix=<optimized out>) at builtin-script.c:2226
#12 0x0000000000482ed1 in run_builtin (p=p@entry=0x907cc8
<commands+360>, argc=argc@entry=3, argv=argv@entry=0x7fffffffe5c0)
at perf.c:390
#13 0x0000000000433a96 in handle_internal_command (argv=0x7fffffffe5c0,
argc=3) at perf.c:451
#14 run_argv (argv=0x7fffffffe340, argcp=0x7fffffffe34c) at perf.c:495
#15 main (argc=3, argv=0x7fffffffe5c0) at perf.c:618
Please have a look at patch:
http://lkml.kernel.org/g/1454296865-19749-1-git-send-email-wangnan0@huawei.com
You should have in the cc-list.
Thank you.
next prev parent reply other threads:[~2016-02-01 3:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 21:02 [PATCH 1/1] broken perf tool on 4.4-rc1 Tong Zhang
2016-01-30 21:20 ` TongZhang
2016-02-01 2:17 ` Wangnan (F)
2016-02-01 3:23 ` Wangnan (F) [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-01-30 21:09 Tong Zhang
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=56AECFCD.3050708@huawei.com \
--to=wangnan0@huawei.com \
--cc=acme@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ztong@vt.edu \
/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