diff options
author | 2018-01-29 17:02:33 -0800 | |
---|---|---|
committer | 2018-01-30 21:54:29 +0100 | |
commit | b3d7ad85b80bbc404635dca80f5b129f6242bc7a (patch) | |
tree | f3d1c6f5676006e25bcd8cf420bd3198657149ee /tools/perf/scripts/python/export-to-postgresql.py | |
parent | x86: Implement array_index_mask_nospec (diff) | |
download | linux-dev-b3d7ad85b80bbc404635dca80f5b129f6242bc7a.tar.xz linux-dev-b3d7ad85b80bbc404635dca80f5b129f6242bc7a.zip |
x86: Introduce barrier_nospec
Rename the open coded form of this instruction sequence from
rdtsc_ordered() into a generic barrier primitive, barrier_nospec().
One of the mitigations for Spectre variant1 vulnerabilities is to fence
speculative execution after successfully validating a bounds check. I.e.
force the result of a bounds check to resolve in the instruction pipeline
to ensure speculative execution honors that result before potentially
operating on out-of-bounds data.
No functional changes.
Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
Suggested-by: Andi Kleen <ak@linux.intel.com>
Suggested-by: Ingo Molnar <mingo@redhat.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-arch@vger.kernel.org
Cc: Tom Lendacky <thomas.lendacky@amd.com>
Cc: Kees Cook <keescook@chromium.org>
Cc: kernel-hardening@lists.openwall.com
Cc: gregkh@linuxfoundation.org
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: alan@linux.intel.com
Link: https://lkml.kernel.org/r/151727415361.33451.9049453007262764675.stgit@dwillia2-desk3.amr.corp.intel.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions