All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sandipan Das <sandipan@linux.vnet.ibm.com>
To: Thomas-Mich Richter <tmricht@linux.ibm.com>,
	acme@kernel.org, jolsa@redhat.com
Cc: linux-kernel@vger.kernel.org, ravi.bangoria@linux.ibm.com,
	naveen.n.rao@linux.vnet.ibm.com,
	Hendrik Brueckner <brueckner@linux.vnet.ibm.com>
Subject: Re: [PATCH] perf tests: Fix regex for record+probe_libc_inet_pton.sh
Date: Fri, 18 May 2018 15:59:13 +0530	[thread overview]
Message-ID: <764aa7ae-dcbe-6311-19fd-3d31b18f1645@linux.vnet.ibm.com> (raw)
In-Reply-To: <be181700-57a5-e4c8-7cd4-88a88b7a51f1@linux.ibm.com>

Hi Thomas,

On 05/18/2018 03:51 PM, Thomas-Mich Richter wrote:
[...]
> 
> This patch fails on s390. I used 4.17.0rc5 + fedora 27 and I get this output:
> 
> 
> [root@p23lp27 perf]# ./perf test 59
> 59: probe libc's inet_pton & backtrace it with ping       : Ok
> [root@p23lp27 linux]# cd ~/linux; patch -p1 < ../inet_pton1 
> (Stripping trailing CRs from patch; use --binary to disable.)
> patching file tools/perf/tests/shell/record+probe_libc_inet_pton.sh
> [root@p23lp27 linux]# cd -; 
> [root@p23lp27 perf]# ./perf test 59
> 59: probe libc's inet_pton & backtrace it with ping       : FAILED!
> [root@p23lp27 perf]#
> 
> Debugging revealed this line as cause of failure:
> 
> 
> FAIL: expected backtrace entry 2 "gaih_inet.*\+0x[[:xdigit:]]+[[:space:]]\(/usr/lib64/libc-2.26.so|inlined\)$" got "fdcb1 gaih_inet.constprop.7 (/usr/lib64/libc-2.26.so)"
> 
> Here is the output of the trace file
> 
> [root@p23lp27 perf]# perf script 
> ping 87291 [001] 96936.231618: probe_libc:inet_pton: (3ff96342378)
>                   142378 __inet_pton (inlined)
>                    fdcb1 gaih_inet.constprop.7 (/usr/lib64/libc-2.26.so)
>                   100189 __GI_getaddrinfo (inlined)
>                     398d main (/usr/bin/ping)
>                    2303d __libc_start_main (/usr/lib64/libc-2.26.so)
>                     457b [unknown] (/usr/bin/ping)
> 
> [root@p23lp27 perf]# 
> 
> Hope this helps
> 

Can you please apply these two patches as well and then re-test?

[1] https://lkml.org/lkml/2018/5/17/112
[2] https://lkml.org/lkml/2018/5/17/113

- Sandipan

  reply	other threads:[~2018-05-18 10:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18  7:24 [PATCH] perf tests: Fix regex for record+probe_libc_inet_pton.sh Sandipan Das
2018-05-18 10:21 ` Thomas-Mich Richter
2018-05-18 10:29   ` Sandipan Das [this message]
2018-05-18 11:09     ` Thomas-Mich Richter
2018-05-18 14:14       ` Arnaldo Carvalho de Melo
2018-05-18 18:24         ` Arnaldo Carvalho de Melo
2018-05-22  6:09         ` Thomas-Mich Richter
2018-05-18 19:21 ` Arnaldo Carvalho de Melo
2018-05-18 19:28   ` Sandipan Das
2018-05-18 19:29   ` Arnaldo Carvalho de Melo
2018-05-18 19:30     ` Arnaldo Carvalho de Melo
2018-07-04  6:57 ` [lkp-robot] [perf tests] 32a4debc7c: perf-sanity-tests.probe_libc's_inet_pton_&_backtrace_it_with_ping.fail kernel test robot
2018-07-04  6:57   ` kernel test robot
2018-07-04 12:37   ` Sandipan Das

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=764aa7ae-dcbe-6311-19fd-3d31b18f1645@linux.vnet.ibm.com \
    --to=sandipan@linux.vnet.ibm.com \
    --cc=acme@kernel.org \
    --cc=brueckner@linux.vnet.ibm.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naveen.n.rao@linux.vnet.ibm.com \
    --cc=ravi.bangoria@linux.ibm.com \
    --cc=tmricht@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.