linux-kernel - Re: [PATCH v15 0/4] trace: Introduce objtrace trigger to trace the 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:   Tue, 29 Nov 2022 11:30:06 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Jeff Xie <xiehuan09@...il.com>
Cc:     mingo@...hat.com, mhiramat@...nel.org, zanussi@...nel.org,
        linux-kernel@...r.kernel.org, chensong_2000@....cn
Subject: Re: [PATCH v15 0/4] trace: Introduce objtrace trigger to trace the
 kernel object

On Wed, 30 Nov 2022 00:09:51 +0800
Jeff Xie <xiehuan09@...il.com> wrote:

> > Now instead of searching the function arguments for "obj", we should just
> > read the obj value at every function and report when it changed, as well as
> > the last function it was still the same. The report will be like the
> > "func_repeats" entry. And instead we can print when the object changes,
> > something like this:
> >
> >               cat-117     [002] ...2.     1.602245: bio_add_page <-ext4_mpage_readpages object:0xffff88811bee4000 value:0x2000 (last value:0x1000 at [002] __bio_add_page <-bio_add_page ts: 1.602245)  
> 
> 
> I'm just curious if we'll see this rewritten version in the next merge
> window  ;-)

Unfortunately, this ended up getting dropped in priority, as my workload
increased internally. :-/

-- Steve