linux-kernel - Re: [PATCH] trace: Add trace any kernel object

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]

Date:   Wed, 20 Oct 2021 15:07:13 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Huan Xie <xiehuan09@...il.com>
Cc:     Masami Hiramatsu <mhiramat@...nel.org>, mingo@...hat.com,
        chenhuacai@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] trace: Add trace any kernel object

On Thu, 21 Oct 2021 00:04:40 +0800
Huan Xie <xiehuan09@...il.com> wrote:

> Thanks. The trigger seems to work in combination with kprobe/uprobe/eprobe.
> 
> I have been trying to implement this feature in recent days, But my
> code does not look very elegant at the moment :-)

Feel free to post what you have. I swear I wont judge you based on your code
;-)

Just add "[RFC]" to the subject of your patches, to let us know it's not
for inclusion.

> 
> It seems the result of 'cat  trace' should also need to be filtered,
> Because it will output the functions we don’t want to care about.

We can work to make it attached to "set_ftrace_pid" and "set_ftrace_filter"
and friends, so that it can easily be filtered.

> 
> I didn't expect this idea to be a relatively large project. :-)

Kernel updates never are what you expect them to be come ;-)

-- Steve