diff options
| author | Kees Cook <keescook@chromium.org> | 2021-11-18 12:22:17 -0800 |
|---|---|---|
| committer | Steven Rostedt (VMware) <rostedt@goodmis.org> | 2021-11-18 20:54:51 -0500 |
| commit | c4c1dbcc09e723295969a62aff401815b7ee15f4 (patch) | |
| tree | 08f09cc6b7516abc2ba752bebb11b3d1685c55e5 /tools/perf/scripts/python/failed-syscalls-by-pid.py | |
| parent | f86b0aaad741c45aba5a84a27277dd56a96808ba (diff) | |
tracing: Use memset_startat() to zero struct trace_iterator
In preparation for FORTIFY_SOURCE performing compile-time and run-time
field bounds checking for memset(), avoid intentionally writing across
neighboring fields.
Use memset_startat() to avoid confusing memset() about writing beyond
the target struct member.
Link: https://lkml.kernel.org/r/20211118202217.1285588-1-keescook@chromium.org
Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions