All of lore.kernel.org
 help / color / mirror / Atom feed
From: <gregkh@linuxfoundation.org>
To: boris.ostrovsky@oracle.com, dwmw@amazon.co.uk,
	gregkh@linuxfoundation.org, jgross@suse.com, tglx@linutronix.de,
	xen-devel@lists.xenproject.org
Cc: stable-commits@vger.kernel.org
Subject: Patch "x86/amd: don't set X86_BUG_SYSRET_SS_ATTRS when running under Xen" has been added to the 4.9-stable tree
Date: Sat, 02 Jun 2018 15:35:44 +0200	[thread overview]
Message-ID: <1527946544105110@kroah.com> (raw)
In-Reply-To: <20180530110958.19413-4-jgross@suse.com>


This is a note to let you know that I've just added the patch titled

    x86/amd: don't set X86_BUG_SYSRET_SS_ATTRS when running under Xen

to the 4.9-stable tree which can be found at:
    http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     x86-amd-don-t-set-x86_bug_sysret_ss_attrs-when-running-under-xen.patch
and it can be found in the queue-4.9 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.


From foo@baz Sat Jun  2 15:10:07 CEST 2018
From: Juergen Gross <jgross@suse.com>
Date: Wed, 30 May 2018 13:09:58 +0200
Subject: x86/amd: don't set X86_BUG_SYSRET_SS_ATTRS when running under Xen
To: stable@vger.kernel.org, xen-devel@lists.xenproject.org
Cc: dwmw@amazon.co.uk, boris.ostrovsky@oracle.com, Juergen Gross <jgross@suse.com>
Message-ID: <20180530110958.19413-4-jgross@suse.com>

From: Juergen Gross <jgross@suse.com>

Upstream commit: def9331a12977770cc6132d79f8e6565871e8e38 ("x86/amd:
don't set X86_BUG_SYSRET_SS_ATTRS when running under Xen")

When running as Xen pv guest X86_BUG_SYSRET_SS_ATTRS must not be set
on AMD cpus.

This bug/feature bit is kind of special as it will be used very early
when switching threads. Setting the bit and clearing it a little bit
later leaves a critical window where things can go wrong. This time
window has enlarged a little bit by using setup_clear_cpu_cap() instead
of the hypervisor's set_cpu_features callback. It seems this larger
window now makes it rather easy to hit the problem.

The proper solution is to never set the bit in case of Xen.

Signed-off-by: Juergen Gross <jgross@suse.com>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Acked-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
 arch/x86/kernel/cpu/amd.c |    5 +++--
 arch/x86/xen/enlighten.c  |    4 +---
 2 files changed, 4 insertions(+), 5 deletions(-)

--- a/arch/x86/kernel/cpu/amd.c
+++ b/arch/x86/kernel/cpu/amd.c
@@ -857,8 +857,9 @@ static void init_amd(struct cpuinfo_x86
 		if (cpu_has(c, X86_FEATURE_3DNOW) || cpu_has(c, X86_FEATURE_LM))
 			set_cpu_cap(c, X86_FEATURE_3DNOWPREFETCH);
 
-	/* AMD CPUs don't reset SS attributes on SYSRET */
-	set_cpu_bug(c, X86_BUG_SYSRET_SS_ATTRS);
+	/* AMD CPUs don't reset SS attributes on SYSRET, Xen does. */
+	if (!cpu_has(c, X86_FEATURE_XENPV))
+		set_cpu_bug(c, X86_BUG_SYSRET_SS_ATTRS);
 }
 
 #ifdef CONFIG_X86_32
--- a/arch/x86/xen/enlighten.c
+++ b/arch/x86/xen/enlighten.c
@@ -473,10 +473,8 @@ static void __init xen_init_cpuid_mask(v
 
 static void __init xen_init_capabilities(void)
 {
-	if (xen_pv_domain()) {
-		setup_clear_cpu_cap(X86_BUG_SYSRET_SS_ATTRS);
+	if (xen_pv_domain())
 		setup_force_cpu_cap(X86_FEATURE_XENPV);
-	}
 }
 
 static void xen_set_debugreg(int reg, unsigned long val)


Patches currently in stable-queue which might be from jgross@suse.com are

queue-4.9/x86-amd-don-t-set-x86_bug_sysret_ss_attrs-when-running-under-xen.patch
queue-4.9/x86-amd-revert-commit-944e0fc51a89c9827b9.patch
queue-4.9/xen-set-cpu-capabilities-from-xen_start_kernel.patch

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-06-02 13:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30 11:09 [PATCH 0/3] Correct 4.9 stable commit 944e0fc51a89c98 Juergen Gross
2018-05-30 11:09 ` [PATCH 1/3] x86/amd: revert commit 944e0fc51a89c9827b9 Juergen Gross
2018-06-02 13:35   ` Patch "x86/amd: revert commit 944e0fc51a89c9827b9" has been added to the 4.9-stable tree gregkh
2018-05-30 11:09 ` [PATCH 1/3] x86/amd: revert commit 944e0fc51a89c9827b9 Juergen Gross
2018-05-30 11:09 ` [PATCH 2/3] xen: set cpu capabilities from xen_start_kernel() Juergen Gross
2018-06-02 13:35   ` Patch "xen: set cpu capabilities from xen_start_kernel()" has been added to the 4.9-stable tree gregkh
2018-07-11  9:15   ` [PATCH 2/3] xen: set cpu capabilities from xen_start_kernel() Woodhouse, David
2018-07-11  9:46     ` Juergen Gross
2018-07-11  9:46     ` Juergen Gross
2018-07-11  9:54       ` Woodhouse, David
2018-05-30 11:09 ` Juergen Gross
2018-05-30 11:09 ` [PATCH 3/3] x86/amd: don't set X86_BUG_SYSRET_SS_ATTRS when running under Xen Juergen Gross
2018-06-02 13:35   ` gregkh [this message]
2018-05-30 11:09 ` Juergen Gross
2018-06-02 13:11 ` [PATCH 0/3] Correct 4.9 stable commit 944e0fc51a89c98 Greg KH
2018-06-02 13:11 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1527946544105110@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=dwmw@amazon.co.uk \
    --cc=jgross@suse.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.