linux-kernel - Re: [PATCH] uprobes: list all active uprobes in the system

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20230114002954.199fe4c699d2ccc0591a4b66@kernel.org>
Date:   Sat, 14 Jan 2023 00:29:54 +0900
From:   Masami Hiramatsu (Google) <mhiramat@...nel.org>
To:     Ravi Bangoria <ravi.bangoria@....com>
Cc:     luolongjun@...wei.com, peterz@...radead.org, mingo@...hat.com,
        acme@...nel.org, mark.rutland@....com,
        alexander.shishkin@...ux.intel.com, jolsa@...nel.org,
        namhyung@...nel.org, linux-perf-users@...r.kernel.org,
        linux-kernel@...r.kernel.org, sangyan@...wei.com,
        luanjianhai@...wei.com, zhuling8@...wei.com, lizongwu@...wei.com,
        luolongjuna@...il.com, rostedt@...dmis.org, mhiramat@...nel.org,
        oleg@...hat.com
Subject: Re: [PATCH] uprobes: list all active uprobes in the system

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

> +cc: Steven, Oleg, Masami
> 
> On 11-Jan-23 4:18 PM, luolongjun@...wei.com wrote:
> > From: Longjun Luo <luolongjun@...wei.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@...nel.org>