linux-kernel - Re: [PATCH v2] tracing/eprobe: Iterate trace

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: <20230818200258.7f318bab352508c54ed53e83@kernel.org>
Date:   Fri, 18 Aug 2023 20:02:58 +0900
From:   Masami Hiramatsu (Google) <mhiramat@...nel.org>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     Chuang Wang <nashuiliang@...il.com>, linux-kernel@...r.kernel.org,
        linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH v2] tracing/eprobe: Iterate trace_eprobe directly

On Wed, 16 Aug 2023 16:08:50 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:

> On Sat, 12 Aug 2023 14:20:19 +0900
> Masami Hiramatsu (Google) <mhiramat@...nel.org> wrote:
> 
> > > At a minimum, let's call it:
> > > 
> > >   for_each_trace_point_eprobe()  
> > 
> > OK, what about "for_each_trace_eprobe_on()"? I would like to clarify
> > 
> > - what type is returned
> > - not all trace_eprobes, but only on the trace_probe.
> > 
> > Thank you,
> 
>  for_each_trace_eprobe_tp() or for_each_trace_tp_eprobe() ?

for_each_trace_eprobe_tp() is OK for me.

Thanks!

> 
> As it only works for a trace_probe.
> 
> -- Steve


-- 
Masami Hiramatsu (Google) <mhiramat@...nel.org>