[PATCH security-next v3 04/29] LSM: Remove initcall tracing

From
Steven Rostedt <rostedt@goodmis.org>
Date
2018-09-30 23:25:36
Also in
linux-arch, linux-doc, lkml
Reply to
Kees Cook, 2018-09-26
On Wed, 26 Sep 2018 11:35:21 -0700
Kees Cook [off-list ref] wrote:
On Wed, Sep 26, 2018 at 9:35 AM, Steven Rostedt [off-list ref] wrote:
quoted
On Mon, 24 Sep 2018 17:18:07 -0700
Kees Cook [off-list ref] wrote:
 
quoted
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.  
I'm not against the change, but how much are they going to "no longer
resemble regular init calls"?  
My take on "regular" init calls is that they're always run, link-time
ordered, etc. The changes proposed here will make it so not all
initialization are run depending on runtime configurations, ordering
will be flexible, etc.
Will it still be a good idea to have a tracepoint for those calls?
Perhaps not an  initcall tracepoint but some other kind?

-- Steve
Thread (82 messages) 82 messages, 7 authors, last reply 2018-10-01
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help