summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorGreg Kroah-Hartman <gregkh@linuxfoundation.org>2023-08-08 20:20:48 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2023-08-08 21:03:51 +0300
commitdd5f2ef16e3c6b83f14b5e620f51f42bc05a5d47 (patch)
tree838e1cc82acd1a93f70ef44a18e98ab7ea9594c6 /arch
parentfa5b932b77c815d0e416612859d5899424bb4212 (diff)
downloadlinux-dd5f2ef16e3c6b83f14b5e620f51f42bc05a5d47.tar.xz
x86: fix backwards merge of GDS/SRSO bit
Stable-tree-only change. Due to the way the GDS and SRSO patches flowed into the stable tree, it was a 50% chance that the merge of the which value GDS and SRSO should be. Of course, I lost that bet, and chose the opposite of what Linus chose in commit 64094e7e3118 ("Merge tag 'gds-for-linus-2023-08-01' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip") Fix this up by switching the values to match what is now in Linus's tree as that is the correct value to mirror. Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch')
-rw-r--r--arch/x86/kernel/cpu/common.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
index f63c8427cf63..d38ae25e7c01 100644
--- a/arch/x86/kernel/cpu/common.c
+++ b/arch/x86/kernel/cpu/common.c
@@ -1244,10 +1244,10 @@ static const __initconst struct x86_cpu_id cpu_vuln_whitelist[] = {
#define RETBLEED BIT(3)
/* CPU is affected by SMT (cross-thread) return predictions */
#define SMT_RSB BIT(4)
-/* CPU is affected by GDS */
-#define GDS BIT(5)
/* CPU is affected by SRSO */
-#define SRSO BIT(6)
+#define SRSO BIT(5)
+/* CPU is affected by GDS */
+#define GDS BIT(6)
static const struct x86_cpu_id cpu_vuln_blacklist[] __initconst = {
VULNBL_INTEL_STEPPINGS(IVYBRIDGE, X86_STEPPING_ANY, SRBDS),