Em Tue, Apr 07, 2015 at 08:22:46AM +0000, Wang Nan escreveu: > perf report and perf annotate are easy to trigger segfault if trace data > contain kernel module information like this: > > # perf report -D -i ./perf.data > ... > 0 0 0x188 [0x50]: PERF_RECORD_MMAP -1/0: [0xffffffbff1018000(0xf068000) @ > 0]: x [test_module] > ... > > # perf report -i ./perf.data --objdump=/path/to/objdump > --kallsyms=/path/to/kallsyms > > perf: Segmentation fault > -------- backtrace -------- > /path/to/perf[0x503478] > /lib64/libc.so.6(+0x3545f)[0x7fb201f3745f] > /path/to/perf[0x499b56]
So, with this patch applied I am seeing this: [root@ssdandy ~]# perf sched record -a Kmod (modules.order) and cpumode (0) inconsistent Kmod (modules.builtin) and cpumode (0) inconsistent Kmod (modules.dep) and cpumode (0) inconsistent Kmod (modules.dep.bin) and cpumode (0) inconsistent Kmod (modules.alias) and cpumode (0) inconsistent Kmod (modules.alias.bin) and cpumode (0) inconsistent Kmod (modules.softdep) and cpumode (0) inconsistent Kmod (modules.symbols) and cpumode (0) inconsistent Kmod (modules.symbols.bin) and cpumode (0) inconsistent Kmod (modules.builtin.bin) and cpumode (0) inconsistent Kmod (modules.devname) and cpumode (0) inconsistent ^C[ perf record: Woken up 1 times to write data ] [ perf record: Captured and wrote 0.465 MB perf.data (1595 samples) ] [root@ssdandy ~]#o Can you please check this? Why do we get these warning for these files? Applied the other patch: -> 28 T 04/07 Wang Nan (8,8K) [PATCH v3 1/2] perf: kmaps: enforce usage of kmaps to protect futher bugs. - Arnaldo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
