From: Masami Hiramatsu <mhiramat@kernel.org>
To: Thomas Richter <tmricht@linux.ibm.com>
Cc: "linux-perf-use." <linux-perf-users@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Sumanth Korikkar <sumanthk@linux.ibm.com>,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: Fedora 33 and perf probe failures
Date: Thu, 19 Nov 2020 10:07:11 +0900 [thread overview]
Message-ID: <20201119100711.2309580850fec6a58142f7f1@kernel.org> (raw)
In-Reply-To: <63cdd43f-c970-6c7e-b322-a41f6d418cf7@linux.ibm.com>
Hi Thomas,
On Wed, 18 Nov 2020 17:37:21 +0100
Thomas Richter <tmricht@linux.ibm.com> wrote:
> I debugged the failure of some perf test cases on Fedora 33. The following
> test cases fail on s390 and x86_64 using
Thanks for the report!
Let me setup Fedora33.
>
> [root@f33 yum.repos.d]# uname -a
> Linux f33 5.9.8-200.fc33.x86_64 #1 SMP Tue Nov 10 21:58:19 UTC 2020
> x86_64 x86_64 x86_64 GNU/Linux
> [root@f33 yum.repos.d]#
>
> [root@f33 yum.repos.d]# perf test -F 74 77 78
> 74: Use vfs_getname probe to get syscall args filenames
> :Failed to write event: Invalid argument
> Error: Failed to add events.
> FAILED!
> 77: Check open filename arg using perf trace + vfs_getname
> :Failed to write event: Invalid argument
> Error: Failed to add events.
> FAILED!
> 78: Add vfs_getname probe to get syscall args filenames
> :Failed to write event: Invalid argument
> Error: Failed to add events.
> FAILED!
> [root@f33 yum.repos.d]#
BTW, do we have vfs_getname in the kernel?
>
> The root cause is the output of perf probe -L which returns:
> [root@f33 yum.repos.d]# perf probe -L getname_flags
> Specified source line is not found.
> Error: Failed to show lines.
Hmm, could you run it with -vvv option?
> [root@f33 yum.repos.d]#
>
> whereas on my Fedora 32 installation this command shows
> [root@t35lp46 perf]# cat /etc/redhat-release
> Fedora release 32 (Thirty Two)
> [root@t35lp46 perf]#
>
> [root@t35lp46 perf]# ./perf probe -L getname_flags | tail -10
> 68 return ERR_PTR(-ENOENT);
> }
> }
>
> 72 result->uptr = filename;
> 73 result->aname = NULL;
> 74 audit_getname(result);
> return result;
> }
>
> [root@t35lp46 perf]#
>
> Any ideas how to fix this? Is this failure related to a missing debuginfod
> setup, even when I have installed the debuginfo packages for the kernel:
If you can find the vmlinux in debuginfo package, could you try
eu-addr2line to find getname_flags?
eu-addr2line -e /somewhere/to/vmlinux getname_flags+0
Thank you,
>
> [root@f33 ~]# perf probe -L getname_flags
> Specified source line is not found.
> Error: Failed to show lines.
> [root@f33 ~]# uname -a
> Linux f33 5.9.8-200.fc33.x86_64 #1 SMP Tue Nov 10 21:58:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
> [root@f33 ~]# rpm -qa | fgrep kernel | fgrep debuginfo
> kernel-debuginfo-common-x86_64-5.9.8-200.fc33.x86_64
> kernel-debuginfo-5.9.8-200.fc33.x86_64
> kernel-tools-debuginfo-5.9.7-200.fc33.x86_64
> [root@f33 ~]#
> ~
>
> Thanks a lot
> --
> Thomas Richter, Dept 3252, IBM s390 Linux Development, Boeblingen, Germany
> --
> Vorsitzender des Aufsichtsrats: Gregor Pillen
> Geschäftsführung: Dirk Wittkopp
> Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2020-11-19 1:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 16:37 Fedora 33 and perf probe failures Thomas Richter
2020-11-19 1:07 ` Masami Hiramatsu [this message]
2020-11-19 8:16 ` Thomas Richter
2020-11-19 13:04 ` Masami Hiramatsu
2020-11-26 13:08 ` Masami Hiramatsu
2020-11-26 17:28 ` Arnaldo Carvalho de Melo
2020-11-27 0:10 ` Masami Hiramatsu
2020-11-27 11:36 ` Arnaldo Carvalho de Melo
2020-11-27 5:48 ` [PATCH 1/2] perf-probe: Fix to die_entrypc() returns error correctly Masami Hiramatsu
2020-11-27 5:48 ` [PATCH 2/2] perf-probe: Change function definition check due to broken dwarf Masami Hiramatsu
2020-11-27 17:36 ` 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=20201119100711.2309580850fec6a58142f7f1@kernel.org \
--to=mhiramat@kernel.org \
--cc=acme@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sumanthk@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).