diff options
| author | Steven Rostedt (VMware) <rostedt@goodmis.org> | 2019-10-11 17:22:50 -0400 |
|---|---|---|
| committer | Steven Rostedt (VMware) <rostedt@goodmis.org> | 2019-10-12 20:48:06 -0400 |
| commit | 17911ff38aa58d3c95c07589dbf5d3564c4cf3c5 (patch) | |
| tree | 0437649533f3c50b4207fd9368bf47ae06bcfe95 /fs/tracefs | |
| parent | 8530dec63e7b486e3761cc3d74a22de301845ff5 (diff) | |
| download | linux-17911ff38aa58d3c95c07589dbf5d3564c4cf3c5.tar.gz linux-17911ff38aa58d3c95c07589dbf5d3564c4cf3c5.tar.bz2 linux-17911ff38aa58d3c95c07589dbf5d3564c4cf3c5.zip | |
tracing: Add locked_down checks to the open calls of files created for tracefs
Added various checks on open tracefs calls to see if tracefs is in lockdown
mode, and if so, to return -EPERM.
Note, the event format files (which are basically standard on all machines)
as well as the enabled_functions file (which shows what is currently being
traced) are not lockde down. Perhaps they should be, but it seems counter
intuitive to lockdown information to help you know if the system has been
modified.
Link: http://lkml.kernel.org/r/CAHk-=wj7fGPKUspr579Cii-w_y60PtRaiDgKuxVtBAMK0VNNkA@mail.gmail.com
Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'fs/tracefs')
0 files changed, 0 insertions, 0 deletions