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: <20221020221255.5b3dffe1@gandalf.local.home>
Date:   Thu, 20 Oct 2022 22:12:55 -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 Fri, 21 Oct 2022 09:43:14 +0800
richard clark <richard.xnu.clark@...il.com> wrote:


> Ah, as you can see that I did it, but the result is not what I
> expected :-). Help?

Looking at the code, I see it does indeed only look at builtin tracepoints.

But if you want one module to have access to the tracepoints of another,
then you can have the first one export it.

EXPORT_SYMBOL_TRACEPOINT_GPL(function_event_a);

And then module b should have access to it.

-- Steve