diff options
| author | Sean Christopherson <seanjc@google.com> | 2021-08-18 08:03:08 -0700 |
|---|---|---|
| committer | Kees Cook <keescook@chromium.org> | 2022-02-13 16:48:04 -0800 |
| commit | 73ab4a3509e6b8f93b87398db2aaabd3c9cbe487 (patch) | |
| tree | 1870f8db63e9f47f2d018f25951879ca3c0ce9fc /drivers/hwtracing/intel_th/msu.c | |
| parent | dfd42facf1e4ada021b939b4e19c935dcdd55566 (diff) | |
| download | linux-stable-73ab4a3509e6b8f93b87398db2aaabd3c9cbe487.tar.gz linux-stable-73ab4a3509e6b8f93b87398db2aaabd3c9cbe487.tar.bz2 linux-stable-73ab4a3509e6b8f93b87398db2aaabd3c9cbe487.zip | |
KVM: x86: Replace memset() "optimization" with normal per-field writes
Explicitly zero select fields in the emulator's decode cache instead of
zeroing the fields via a gross memset() that spans six fields. gcc and
clang are both clever enough to batch the first five fields into a single
quadword MOV, i.e. memset() and individually zeroing generate identical
code.
Removing the wart also prepares KVM for FORTIFY_SOURCE performing
compile-time and run-time field bounds checking for memset().
No functional change intended.
Reported-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Sean Christopherson <seanjc@google.com>
Link: https://lore.kernel.org/lkml/YR0jIEzEcUom/7rd@google.com
Signed-off-by: Kees Cook <keescook@chromium.org>
Diffstat (limited to 'drivers/hwtracing/intel_th/msu.c')
0 files changed, 0 insertions, 0 deletions