Hi Xiaolong,

On 07/04/2018 12:27 PM, kernel test robot wrote:
> 
> FYI, we noticed the following commit (built with gcc-7):
> 
> commit: 32a4debc7c89ee5e29c0bbdfdd3ae0ce0e01057f ("[PATCH] perf tests: Fix 
> regex for record+probe_libc_inet_pton.sh")
> url: 
> https://github.com/0day-ci/linux/commits/Sandipan-Das/perf-tests-Fix-regex-for-record-probe_libc_inet_pton-sh/20180521-130408
> 
> 
> in testcase: perf-sanity-tests
> with following parameters:
> 
>       perf_compiler: gcc
> 
> 
> 
> on test machine: qemu-system-x86_64 -enable-kvm -cpu kvm64,+ssse3 -smp 2 -m 8G
> 
> caused below changes (please refer to attached dmesg/kmsg for entire 
> log/backtrace):
> 
> 
> 2018-05-22 17:41:14 sudo 
> /usr/src/linux-perf-x86_64-fedora-25-32a4debc7c89ee5e29c0bbdfdd3ae0ce0e01057f/tools/perf/perf
>  test 62
> 62: probe libc's inet_pton & backtrace it with ping       : FAILED!
> 
> 

This patch has the following dependencies which seem to be missing from your 
source tree.

7903a7086723 ("perf script: Show symbol offsets by default")
19610184693c ("perf script: Show virtual addresses instead of offsets")

Output without these patches:

  62: probe libc's inet_pton & backtrace it with ping       :
  --- start ---
  test child forked, pid 10323
  ping 10340 [001] 888647.764907: probe_libc:inet_pton: (7fe66cbc2220)
  132220 __GI___inet_pton (/usr/lib64/libc-2.25.so)
  FAIL: expected backtrace entry 1 
".*inet_pton\+0x[[:xdigit:]]+[[:space:]]\(/usr/lib64/libc-2.25.so|inlined\)$" 
got "132220 __GI___inet_pton (/usr/lib64/libc-2.25.so)"
  test child finished with -1
  ---- end ----
  probe libc's inet_pton & backtrace it with ping: FAILED!


Output with these patches:

  62: probe libc's inet_pton & backtrace it with ping       :
  --- start ---
  test child forked, pid 13155
  ping 13172 [000] 888783.582767: probe_libc:inet_pton: (7f2afe5ce220)
  7f2afe5ce220 __GI___inet_pton+0x0 (/usr/lib64/libc-2.25.so)
  7f2afe593ebd getaddrinfo+0x11d (/usr/lib64/libc-2.25.so)
  55b725fd8c71 main+0x891 (/usr/bin/ping)
  test child finished with 0
  ---- end ----
  probe libc's inet_pton & backtrace it with ping: Ok


--
With Regards,
Sandipan

Reply via email to