linux-kernel - Re: [ftrace/kprobes PATCH 3/3] tracing/kprobes: Allow kprobe-events to record module symbol

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20181003151227.4a730dcb@gandalf.local.home>
Date:   Wed, 3 Oct 2018 15:12:27 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Masami Hiramatsu <mhiramat@...nel.org>
Cc:     Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
        Dan Carpenter <dan.carpenter@...cle.com>
Subject: Re: [ftrace/kprobes PATCH 3/3] tracing/kprobes: Allow kprobe-events
 to record module symbol

On Wed, 29 Aug 2018 01:18:43 +0900
Masami Hiramatsu <mhiramat@...nel.org> wrote:

> Allow kprobe-events to record module symbols.
> 
> Since data symbols in a non-loaded module doesn't exist, it fails to
> define such symbol as an argument of kprobe-event. But if the kprobe
> event is defined on that module, we can defer to resolve the symbol
> address.
> 
> Note that if given symbol is not found, the event is kept unavailable.
> User can enable it but the event is not recorded.
> 
>

Hi Masami,

The first two patches look like they should be applied now and marked
for stable, as they are fixes. This patch looks like an added feature,
and will go into the next merge window.

Is that what you think too?

Thanks!

-- Steve