linux-kernel - Re: [PATCH 0/1] tracing: Provide more parseable hist trigger output

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] [day] [month] [year] [list]

Date:   Mon, 16 Aug 2021 11:25:08 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Tom Zanussi <zanussi@...nel.org>
Cc:     Masami Hiramatsu <mhiramat@...nel.org>, bristot@...nel.org,
        linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org
Subject: Re: [PATCH 0/1] tracing: Provide more parseable hist trigger output

On Fri, 13 Aug 2021 10:31:03 -0500
Tom Zanussi <zanussi@...nel.org> wrote:

> > $ echo 1 > /sys/kernel/tracing/options/hist-json
> > 
> > This will no need to add additional pseudo file but just add an
> > option to
> > the ftrace.
> >   
> 
> That sounds like a good idea, thanks for the suggestion!

My only worry about this approach is that it affects all events in the
instance (please make this an instance option).

But I think I still rather have it affecting all events in an instance
than to bloat the directories with yet-another-file.

Yeah, make it an option.

Thanks!

-- Steve