linux-kernel - Re: Question about 'for_each_kernel

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: <20221020111439.76e72230@gandalf.local.home>
Date:   Thu, 20 Oct 2022 11:14:39 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     richard clark <richard.xnu.clark@...il.com>
Cc:     bristot@...nel.org, linux-trace-devel@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: Question about 'for_each_kernel_tracepoint(...)' function

On Thu, 20 Oct 2022 17:32:57 +0800
richard clark <richard.xnu.clark@...il.com> wrote:

> Hi,
> Can this function only find the trace points defined in the kernel

It should find all tracepoints.

> image? I want to define a trace event in my kernel module A, then B
> module to register a probe callback function for that event TP in A. I
> want to kick off a timer in A and call the traced function
> periodically, thus I can monitor the events happening in A from B.

You could also export the tracepoint from A and reference it directly in B.

> 
> Can I do that, is it possible?
> 

Try it and find out. Why ask?

-- Steve