Messages in this thread | | | From | Kees Cook <> | Date | Mon, 1 Oct 2018 15:38:55 -0700 | Subject | Re: [PATCH security-next v3 04/29] LSM: Remove initcall tracing |
| |
On Mon, Oct 1, 2018 at 2:23 PM, Steven Rostedt <rostedt@goodmis.org> wrote: > On Mon, 1 Oct 2018 14:07:55 -0700 > John Johansen <john.johansen@canonical.com> wrote: > >> On 09/24/2018 05:18 PM, Kees Cook wrote: >> > This partially reverts commit 58eacfffc417 ("init, tracing: instrument >> > security and console initcall trace events") since security init calls >> > are about to no longer resemble regular init calls. >> > >> > Cc: James Morris <jmorris@namei.org> >> > Cc: "Serge E. Hallyn" <serge@hallyn.com> >> > Cc: Abderrahmane Benbachir <abderrahmane.benbachir@polymtl.ca> >> > Cc: Steven Rostedt (VMware) <rostedt@goodmis.org> >> > Cc: linux-security-module@vger.kernel.org >> > Signed-off-by: Kees Cook <keescook@chromium.org> >> >> >> Reviewed-by: John Johansen <john.johansen@canonical.com> >> >> though I do think it would be a good idea to add a new set >> of trace points, but that can come as a separate patch >> >> > > Agreed.
BTW, how would this look? I'm not familiar with adding new tracepoints...
-Kees
-- Kees Cook Pixel Security
| |