public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: He Kuang <hekuang@huawei.com>
To: <a.p.zijlstra@chello.nl>, <paulus@samba.org>, <mingo@redhat.com>,
	<acme@kernel.org>, <ericvh@gmail.com>, <rminnich@sandia.gov>,
	<lucho@ionkov.net>
Cc: <wangnan0@huawei.com>, <linux-kernel@vger.kernel.org>
Subject: [BUG] uprobe: failed to work on 9pfs
Date: Fri, 6 Mar 2015 13:18:47 +0800	[thread overview]
Message-ID: <54F938B7.20700@huawei.com> (raw)

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.


             reply	other threads:[~2015-03-06  5:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06  5:18 He Kuang [this message]
2015-03-06  8:50 ` [BUG] uprobe: failed to work on 9pfs Peter Zijlstra

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=54F938B7.20700@huawei.com \
    --to=hekuang@huawei.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=ericvh@gmail.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