From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug kprobes/28557] New: dwflpp not getting inline entry point of xfs:xfs_ilock
Date: Sat, 06 Nov 2021 20:40:55 +0000 [thread overview]
Message-ID: <bug-28557-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28557
Bug ID: 28557
Summary: dwflpp not getting inline entry point of xfs:xfs_ilock
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: kprobes
Assignee: systemtap at sourceware dot org
Reporter: me at serhei dot io
Target Milestone: ---
Manifests on kernel 5.14.0-1.el9.x86_64.
$ /opt/stap-checkout/stap_install/bin/stap -vvvve 'probe begin {
println("running") } probe module("xfs").function("xfs_ilock") { exit() }'
running
<indefinite hang>
SHOULD BE
parse 'xfs_ilock', func 'xfs_ilock'
pattern 'xfs' matches module 'xfs'
focused on module 'xfs' = [0x10000-0x144c28, bias 0 file
/usr/lib/debug/usr/lib/modules/4.18.0-348.4.el8.x86_64/kernel/fs/xfs/xfs.ko.debug
ELF machine |x86_64 (code 62)
focused on module 'xfs'
selected function xfs_ilock
xfs_ilock = dwfl_module_addrinfo(entrypc=0x85760 + (nil))
added to filtered_functions (dieoffset: 0x8efee9)
checking instances of inline xfs_ilock
selected inline instance of xfs_ilock
entry-pc lookup (dwarf_entrypc dieoffset: 0x8f014e) = 0x85797 (rc 0)
added to filtered_inlines (dieoffset: 0x8f014e)
selected function xfs_ilock
xfs_ilock = dwfl_module_addrinfo(entrypc=0x85760 + (nil))
added to filtered_functions (dieoffset: 0x8efee9)
checking instances of inline xfs_ilock
selected inline instance of xfs_ilock
entry-pc lookup (dwarf_entrypc dieoffset: 0x8f014e) = 0x85797 (rc 0)
added to filtered_inlines (dieoffset: 0x8f014e)
probe xfs_ilock@fs/xfs/xfs_inode.c:166 module=xfs reloc=.text pc=0x85760
function exit is defined in new-tapset-file
/opt/stap-checkout/stap_install/share/systemtap/tapset/logging.stp
querying entrypc 0x85797 of instance of inline 'xfs_ilock'
probe xfs_ilock@fs/xfs/xfs_inode.c:166 module=xfs reloc=.text pc=0x85797
symbol resolution for derived-probe probe
module("xfs").function("xfs_ilock@fs/xfs/xfs_inode.c:166") /*
pc=<xfs:xfs_ilock+0> */ /* <-
module("xfs").function("xfs_ilock@fs/xfs/xfs_inode.c:166") */{
exit();
}
symbol resolution for derived-probe probe
module("xfs").function("xfs_ilock@fs/xfs/xfs_inode.c:166") /*
pc=<xfs:xfs_ilock+55> */ /* <-
module("xfs").function("xfs_ilock@fs/xfs/xfs_inode.c:166") */{
exit();
}
INSTEAD
parse 'xfs_ilock', func 'xfs_ilock'
pattern 'xfs' matches module 'xfs'
focused on module 'xfs' = [0x10000-0x187048, bias 0 file
/lib/modules/5.14.0-1.el9.x86_64/kernel/fs
/xfs/xfs.ko.xz ELF machine |x86_64 (code 62)
focused on module 'xfs'
selected function xfs_ilock
xfs_ilock = dwfl_module_addrinfo(entrypc=0x8ea40 + (nil))
added to filtered_functions (dieoffset: 0x655c15)
selected function xfs_ilock
xfs_ilock = dwfl_module_addrinfo(entrypc=0x8ea40 + (nil))
added to filtered_functions (dieoffset: 0x655c15)
probe xfs_ilock@fs/xfs/xfs_inode.c:164 module=xfs reloc=.text pc=0x8ea40
function exit is defined in new-tapset-file
/opt/stap-checkout/stap_install/share/systemtap/tapset/logging.stp
symbol resolution for derived-probe probe
module("xfs").function("xfs_ilock@fs/xfs/xfs_inode.c:164") /*
pc=<xfs:xfs_ilock+0> */ /* <-
module("xfs").function("xfs_ilock@fs/xfs/xfs_inode.c:164") */{
exit();
}
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-11-06 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 20:40 me at serhei dot io [this message]
2021-11-11 13:41 ` [Bug kprobes/28557] unable to probe function in kernel module (xfs:xfs_ilock &others?) me at serhei dot io
2021-11-14 21:31 ` fche 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-28557-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).