From: Josef Bacik <josef@toxicpanda.com>
To: Howard McLauchlan <hmclauchlan@fb.com>
Cc: linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
kernel-team@fb.com, Yonghong Song <yhs@fb.com>,
Josef Bacik <jbacik@fb.com>, Omar Sandoval <osandov@osandov.com>
Subject: Re: [PATCH] uprobe: add support for overlayfs
Date: Mon, 5 Mar 2018 14:59:05 -0500 [thread overview]
Message-ID: <20180305195904.sliaqqv4dzuebque@destiny> (raw)
In-Reply-To: <20180228004014.445-1-hmclauchlan@fb.com>
On Tue, Feb 27, 2018 at 04:40:14PM -0800, Howard McLauchlan wrote:
> uprobes cannot successfully attach to binaries located in a directory
> mounted with overlayfs.
>
> To verify, create directories for mounting overlayfs
> (upper,lower,work,merge), move some binary into merge/ and use readelf
> to obtain some known instruction of the binary. I used /bin/true and the
> entry instruction(0x13b0):
>
> $ mount -t overlay overlay -o lowerdir=lower,upperdir=upper,workdir=work merge
> $ cd /sys/kernel/debug/tracing
> $ echo 'p:true_entry PATH_TO_MERGE/merge/true:0x13b0' > uprobe_events
> $ echo 1 > events/uprobes/true_entry/enable
>
> This returns 'bash: echo: write error: Input/output error' and dmesg
> tells us 'event trace: Could not enable event true_entry'
>
> This change makes create_trace_uprobe() look for the real inode of a
> dentry. In the case of normal filesystems, this simplifies to just
> returning the inode. In the case of overlayfs(and similar fs) we will
> obtain the underlying dentry and corresponding inode, upon which uprobes
> can successfully register.
>
> Running the example above with the patch applied, we can see that the
> uprobe is enabled and will output to trace as expected.
>
> Signed-off-by: Howard McLauchlan <hmclauchlan@fb.com>
Reviewed-by: Josef Bacik <jbacik@fb.com>
Thanks,
Josef
next prev parent reply other threads:[~2018-03-05 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 0:40 Howard McLauchlan
2018-03-05 19:59 ` Josef Bacik [this message]
2018-04-10 23:10 Howard McLauchlan
2018-04-11 0:00 ` Steven Rostedt
2018-04-11 2:13 ` Masami Hiramatsu
2018-04-11 14:27 ` Srikar Dronamraju
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=20180305195904.sliaqqv4dzuebque@destiny \
--to=josef@toxicpanda.com \
--cc=hmclauchlan@fb.com \
--cc=jbacik@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=osandov@osandov.com \
--cc=rostedt@goodmis.org \
--cc=yhs@fb.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
all inboxes | Powered by JetHome®