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: <20230811154523.61e67cc3@gandalf.local.home>
Date:   Fri, 11 Aug 2023 15:45:23 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Chuang Wang <nashuiliang@...il.com>
Cc:     Masami Hiramatsu <mhiramat@...nel.org>,
        linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH v2] tracing/eprobe: Iterate trace_eprobe directly

On Fri, 11 Aug 2023 16:12:39 +0800
Chuang Wang <nashuiliang@...il.com> wrote:

> +
> +#define for_each_trace_eprobe_on_trace_probe(ep, _tp) \
> +	list_for_each_entry(ep, trace_probe_probe_list(_tp), tp.list)
> +

As I replied to the other patch, but after this one was sent (sorry, I was
hyperfocused on my work the last couple of days and was not reading email,
so my INBOX is a bit full). I really hate the verbosity of that name.

At a minimum, let's call it:

  for_each_trace_point_eprobe()

-- Steve