From: "jeffliu.js.1999 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/29388] New: Support using systemtap with overlayfs
Date: Wed, 20 Jul 2022 01:41:06 +0000 [thread overview]
Message-ID: <bug-29388-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29388
Bug ID: 29388
Summary: Support using systemtap with overlayfs
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: jeffliu.js.1999 at gmail dot com
Target Milestone: ---
When using systemtap with overlay filesystem, we need to get real inode and
pass it into uprobe_register function. Otherwise, there will be an inode error.
To fix the problem, we need to modify 4 places in runtime/linux/uprobes-inode.c
file to let systemtap get the real inode value. The following is the way to
support this feature.
733c733
--- inode = vm_file->f_path.dentry->d_inode;
+++ inode = d_real_inode(vm_file->f_path.dentry);
915c915
--- p->inode = dentry->d_inode;
+++ p->inode = d_real_inode(dentry);
928c928
--- offset, vm_flags, dentry->d_inode);
+++ offset, vm_flags, d_real_inode(dentry));
938c938
--- rc = stapiu_change_semaphore_plus(c, task, addr, dentry->d_inode);
+++ rc = stapiu_change_semaphore_plus(c, task, addr, d_real_inode(dentry));
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-07-20 1:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 1:41 jeffliu.js.1999 at gmail dot com [this message]
2022-07-20 1:41 ` [Bug runtime/29388] " jeffliu.js.1999 at gmail dot com
2022-07-20 1:43 ` jeffliu.js.1999 at gmail dot com
2022-07-20 1:48 ` 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-29388-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).