From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752947AbbCFFTk (ORCPT ); Fri, 6 Mar 2015 00:19:40 -0500 Received: from szxga02-in.huawei.com ([119.145.14.65]:11608 "EHLO szxga02-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752500AbbCFFTi (ORCPT ); Fri, 6 Mar 2015 00:19:38 -0500 Message-ID: <54F938B7.20700@huawei.com> Date: Fri, 6 Mar 2015 13:18:47 +0800 From: He Kuang User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: , , , , , , CC: , Subject: [BUG] uprobe: failed to work on 9pfs Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.110.54.65] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.