linux-kernel - Re: [PATCH 0/4 v2] init, tracing: Add initcall trace events

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]

Date:   Fri, 6 Apr 2018 15:46:02 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Frederic Weisbecker <fweisbec@...il.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        "Joel Fernandes (Google)" <joel.opensrc@...il.com>,
        Abderrahmane Benbachir <abderrahmane.benbachir@...ymtl.ca>
Subject: Re: [PATCH 0/4 v2] init, tracing: Add initcall trace events

On Fri, 6 Apr 2018 21:34:24 +0200
Peter Zijlstra <peterz@...radead.org> wrote:

> On Fri, Apr 06, 2018 at 03:19:23PM -0400, Steven Rostedt wrote:
> > 
> > Peter, Andrew,
> > 
> > This keeps initcall_debug printing printk()s, but adds the feature of
> > those locations also being trace events. Are you OK if I add this?  
> 
> Yeah, I don't see any real problems with it.

Thanks!

Andrew, do you?

-- Steve