From: Peter Zijlstra <peterz@infradead.org>
To: He Kuang <hekuang@huawei.com>
Cc: paulus@samba.org, mingo@redhat.com, acme@kernel.org,
ericvh@gmail.com, rminnich@sandia.gov, lucho@ionkov.net,
wangnan0@huawei.com, linux-kernel@vger.kernel.org
Subject: Re: [BUG] uprobe: failed to work on 9pfs
Date: Fri, 6 Mar 2015 09:50:17 +0100 [thread overview]
Message-ID: <20150306085017.GW21418@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <54F938B7.20700@huawei.com>
On Fri, Mar 06, 2015 at 01:18:47PM +0800, He Kuang wrote:
> Uprobe uses inode address to index all registered uprobes in a
> rb_tree, this works well in most filesystems but failed on 9pfs.
>
> 9pfs allocate more than one vfs inode to the same file, the inode
> address when we create uprobe is not same as the inode address we
> run later. As a result, neither perf record nor events/uprobe can
> capture the predefined uprobe events.
How does 9pfs work with the vfs/mm in this regard? The file cache very
much assumes the same thing uprobes does.
File caching is per inode, so if you have multiple inodes on the same
file you get multiple copies of your data with all sorts of braindamaged
corruption as a result.
I would very much chalk this up to 9pfs being insane.
prev parent reply other threads:[~2015-03-06 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 5:18 [BUG] uprobe: failed to work on 9pfs He Kuang
2015-03-06 8:50 ` Peter Zijlstra [this message]
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=20150306085017.GW21418@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=ericvh@gmail.com \
--cc=hekuang@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=rminnich@sandia.gov \
--cc=wangnan0@huawei.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