Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Sat, 14 Jan 2023 00:29:54 +0900
From:   Masami Hiramatsu (Google) <mhiramat@kernel.org>
To:     Ravi Bangoria <ravi.bangoria@amd.com>
Cc:     luolongjun@huawei.com, peterz@infradead.org, mingo@redhat.com,
        acme@kernel.org, mark.rutland@arm.com,
        alexander.shishkin@linux.intel.com, jolsa@kernel.org,
        namhyung@kernel.org, linux-perf-users@vger.kernel.org,
        linux-kernel@vger.kernel.org, sangyan@huawei.com,
        luanjianhai@huawei.com, zhuling8@huawei.com, lizongwu@huawei.com,
        luolongjuna@gmail.com, rostedt@goodmis.org, mhiramat@kernel.org,
        oleg@redhat.com
Subject: Re: [PATCH] uprobes: list all active uprobes in the system
Message-Id: <20230114002954.199fe4c699d2ccc0591a4b66@kernel.org>
In-Reply-To: <b4109593-1aa9-bf7a-cb1b-3ccd586f31d6@amd.com>
References: <20230111104825.1945418-1-luolongjun@huawei.com>
        <b4109593-1aa9-bf7a-cb1b-3ccd586f31d6@amd.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Fri, 13 Jan 2023 09:33:41 +0530
Ravi Bangoria <ravi.bangoria@amd.com> wrote:

> +cc: Steven, Oleg, Masami
> 
> On 11-Jan-23 4:18 PM, luolongjun@huawei.com wrote:
> > From: Longjun Luo <luolongjun@huawei.com>
> > 
> > Since uprobes will replace instructions in the process
> > memory, it is necessary to provide one way to list
> > all active uprobes. One can access this file through
> > /sys/kernel/debug/uprobes/list.
> > 
> > Output looks like this
> > =====================
> > inode+offset/ref_ctr_offset    4160760670+0x30a10/0x0
> >     ref                        1
> >     register_rwsem             (unlocked)
> >     consumer_rwsem             (unlocked)
> >     consumers-1
> >         handler                0xffffffffc03ee02e(handler) uprobe
> >         ret_handler            0x0000000000000000( )
> >         filter                 0xffffffffc03ee010(filter) uprobe
> >     consumers-2
> >         handler                0xffffffffc03e902e(handler_1) uprobe_1
> >         ret_handler            0x0000000000000000( )
> >         filter                 0xffffffffc03e9010(filter_1) uprobe_1
> 
> You can list uprobes via /sys/kernel/tracing/uprobe_events. Any specific reason
> to introduce another way?

Note that /sys/kernel/tracing/uprobe_events is only for the uprobes defined
by ftrace, it doesn't include the uprobes registered by out-of-tree modules.

Thank you,

> 
> Thanks,
> Ravi


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>