From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/31404] New: Systemtap unable to find kernel.trace("*") probe points on Fedora rawhide Linux 6.8 kernels
Date: Wed, 21 Feb 2024 14:47:04 +0000 [thread overview]
Message-ID: <bug-31404-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31404
Bug ID: 31404
Summary: Systemtap unable to find kernel.trace("*") probe
points on Fedora rawhide Linux 6.8 kernels
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: wcohen at redhat dot com
Target Milestone: ---
When reviewing the "make installcheck" results on Fedora rawhide. I found that
a number of the tests using the tracepoint probe points were failing. For
example:
Running
/home/wcohen/systemtap_write/systemtap/testsuite/systemtap.base/bz1027459.exp
...
spawn stap -wP
/home/wcohen/systemtap_write/systemtap/testsuite/systemtap.base/bz1027459.stp
semantic error: while resolving probe point: identifier 'kernel' at
/home/wcohen/systemtap_write/install/share/systemtap/tapset/linux/sysc_clone.stp:131:26
source: probe tp_syscall.clone = kernel.trace("sys_enter")
^
semantic error: no match
Pass 2: analysis failed. [man error::pass2]
Number of similar error messages suppressed: 2.
Rerun with -v to see them.
FAIL: bz1027459 -p5 (0)
The probe point can be seen with "perf list tracepoint", but doesn't show up
with systemtap:
[wcohen@rawhide systemtap]$ uname -a
Linux rawhide 6.8.0-0.rc5.41.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Feb 19
14:05:40 UTC 2024 x86_64 GNU/Linux
[wcohen@rawhide systemtap]$ sudo perf list tracepoint |grep raw
[sudo] password for wcohen:
raw_syscalls:sys_enter [Tracepoint event]
raw_syscalls:sys_exit [Tracepoint event]
[wcohen@rawhide systemtap]$ ../install/bin/stap -L 'kernel.trace("sys_enter")'
[wcohen@rawhide systemtap]$
On Fedora 39 systemtap can find the tracepoints:
wcohen@fedora39:~/systemtap_write/systemtap$ uname -a
Linux fedora39 6.7.5-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Feb 17 17:20:08
UTC 2024 x86_64 GNU/Linux
wcohen@fedora39:~/systemtap_write/systemtap$ sudo perf list tracepoint |grep
raw
raw_syscalls:sys_enter [Tracepoint event]
raw_syscalls:sys_exit [Tracepoint event]
wcohen@fedora39:~/systemtap_write/systemtap$ ../install/bin/stap -L
'kernel.trace("sys_enter")'
kernel.trace("raw_syscalls:sys_enter") $regs:struct pt_regs* $id:long int
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2024-02-21 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 14:47 wcohen at redhat dot com [this message]
2024-02-28 14:49 ` [Bug translator/31404] " wcohen at redhat dot com
2024-02-28 15:52 ` wcohen at redhat dot com
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=bug-31404-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).