linux-kernel - Re: [RFC][PATCH v4 1/2] 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]

Message-ID: <20211101111214.1710bfb3@gandalf.local.home>
Date:   Mon, 1 Nov 2021 11:12:14 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Jeff Xie <xiehuan09@...il.com>
Cc:     mhiramat@...nel.org, mingo@...hat.com, zanussi@...nel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH v4 1/2] trace: Add trace any kernel object

On Mon,  1 Nov 2021 23:07:59 +0800
Jeff Xie <xiehuan09@...il.com> wrote:

> Introduce a method based on function tracer to trace any object and get
> the value of the object dynamically. the object can from the dynamic event
> (kprobe_event/uprobe_event) or the static event(tracepoint).
> 
> Usage:
> When using the kprobe event, only need to set the objtrace(a new trigger),
> we can get the value of the object. The object is from the setting of the 
> kprobe event.

Hi Jeff,

I just wanted to let you know that because the merge window just opened
(Linus released 5.15 and is now accepting changes for 5.16), I most likely
wont have any time to review your changes while the merge window is open
(for the next two weeks).

Please do not take my lack of responses during this time as ignoring you.
I'm just going to be overwhelmed with getting things right, and this merge
window is going to be a bit tougher for me than other merge windows.

Thanks,

-- Steve