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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200228185143.GA2904@kernel.org>
Date:   Fri, 28 Feb 2020 15:51:43 -0300
From:   Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
To:     Jiri Olsa <jolsa@...hat.com>
Cc:     Masami Hiramatsu <mhiramat@...nel.org>,
        Adrian Hunter <adrian.hunter@...el.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>,
        Steven Rostedt <rostedt@...dmis.org>,
        Borislav Petkov <bp@...en8.de>,
        "H . Peter Anvin" <hpa@...or.com>, x86@...nel.org,
        Mark Rutland <mark.rutland@....com>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        Mathieu Poirier <mathieu.poirier@...aro.org>,
        Leo Yan <leo.yan@...aro.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V3 03/13] kprobes: Add symbols for kprobe insn pages

Em Fri, Feb 28, 2020 at 06:20:04PM +0100, Jiri Olsa escreveu:
> On Fri, Feb 28, 2020 at 11:36:00PM +0900, Masami Hiramatsu wrote:
> > On Fri, 28 Feb 2020 15:51:15 +0200
> > Adrian Hunter <adrian.hunter@...el.com> wrote:
> > > 	# perf probe __schedule
> > > 	Added new event:
> > > 	  probe:__schedule     (on __schedule)
> > > 	# cat /proc/kallsyms | grep '\[kprobe\]'
> > > 	ffffffffc0035000 t kprobe_insn_page     [kprobe]
> > > 	ffffffffc0054000 t kprobe_optinsn_page  [kprobe]

> > Could you make the module name as [kprobes] ?
> > BTW, it seems to pretend to be a module, but is there no concern of
> > confusing users? Shouldn't it be [*kprobes] so that it is non-exist
> > module name?
 
> note we already have bpf symbols as [bpf] module

That bracket-wrapped convention by now is not module related, but
instead non-main-kernel :-) If one wants to enumerate the modules in the
system, then use /proc/modules, then, to get the symbols for it, look at
symbols in /proc/kallsyms in that [ start, start + module size ] range
and strip whatever comes after '[' :-)

- Arnaldo

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ