diff options
author | 2021-05-24 21:36:48 -0700 | |
---|---|---|
committer | 2022-02-13 16:48:04 -0800 | |
commit | 9ed0a59c0cbb663ea09588322498499a937d08fa (patch) | |
tree | 5b15990b47663467ab6fff08328a645671e2038b /scripts/gdb/linux/utils.py | |
parent | KVM: x86: Replace memset() "optimization" with normal per-field writes (diff) | |
download | wireguard-linux-9ed0a59c0cbb663ea09588322498499a937d08fa.tar.xz wireguard-linux-9ed0a59c0cbb663ea09588322498499a937d08fa.zip |
intel_th: msu: Use memset_startat() for clearing hw header
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() so memset() doesn't get confused about writing
beyond the destination member that is intended to be the starting point
of zeroing through the end of the struct.
Acked-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Link: https://lore.kernel.org/lkml/87sfyzi97l.fsf@ashishki-desk.ger.corp.intel.com
Signed-off-by: Kees Cook <keescook@chromium.org>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions