linux-kernel - [for-next][PATCH 3/4] init, tracing: Have printk come through the trace events for initcall

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: <20180408201204.143567228@goodmis.org>
Date:   Sun, 08 Apr 2018 16:10:03 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     linux-kernel@...r.kernel.org
Cc:     Ingo Molnar <mingo@...nel.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: [for-next][PATCH 3/4] init, tracing: Have printk come through the trace events for
 initcall_debug

View attachment "0003-init-tracing-Have-printk-come-through-the-trace-even.patch" of type "text/plain" (3454 bytes)