From: Andrew Cooper <andrew.cooper3@citrix.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Xen-devel <xen-devel@lists.xen.org>,
David Vrabel <david.vrabel@citrix.com>,
Rusty Russell <rusty@rustcorp.com.au>,
"Thomas Gleixner" <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
<x86@kernel.org>, <linux-kernel@vger.kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
<lguest@lists.ozlabs.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH] x86/cpu: Fix SMAP check in PVOPS environments
Date: Tue, 17 Nov 2015 14:59:24 +0000 [thread overview]
Message-ID: <564B40CC.4030304@citrix.com> (raw)
In-Reply-To: <1433323874-6927-1-git-send-email-andrew.cooper3@citrix.com>
Ping?
None of the discussion on this thread altered the contents of this
patch, and the bug is still present.
~Andrew
On 03/06/15 10:31, Andrew Cooper wrote:
> There appears to be no formal statement of what pv_irq_ops.save_fl() is
> supposed to return precisely. Native returns the full flags, while lguest and
> Xen only return the Interrupt Flag, and both have comments by the
> implementations stating that only the Interrupt Flag is looked at. This may
> have been true when initially implemented, but no longer is.
>
> To make matters worse, the Xen PVOP leaves the upper bits undefined, making
> the BUG_ON() undefined behaviour. Experimentally, this now trips for 32bit PV
> guests on Broadwell hardware. The BUG_ON() is consistent for an individual
> build, but not consistent for all builds. It has also been a sitting timebomb
> since SMAP support was introduced.
>
> Use native_save_fl() instead, which will obtain an accurate view of the AC
> flag.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Reviewed-by: David Vrabel <david.vrabel@citrix.com>
> Tested-by: Rusty Russell <rusty@rustcorp.com.au>
> CC: Thomas Gleixner <tglx@linutronix.de>
> CC: Ingo Molnar <mingo@redhat.com>
> CC: H. Peter Anvin <hpa@zytor.com>
> CC: x86@kernel.org
> CC: linux-kernel@vger.kernel.org
> CC: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> CC: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> CC: xen-devel <xen-devel@lists.xen.org>
> CC: lguest@lists.ozlabs.org
> CC: stable@vger.kernel.org
> ---
> arch/x86/kernel/cpu/common.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
> index a62cf04..4f2fded 100644
> --- a/arch/x86/kernel/cpu/common.c
> +++ b/arch/x86/kernel/cpu/common.c
> @@ -291,10 +291,9 @@ __setup("nosmap", setup_disable_smap);
>
> static __always_inline void setup_smap(struct cpuinfo_x86 *c)
> {
> - unsigned long eflags;
> + unsigned long eflags = native_save_fl();
>
> /* This should have been cleared long ago */
> - raw_local_save_flags(eflags);
> BUG_ON(eflags & X86_EFLAGS_AC);
>
> if (cpu_has(c, X86_FEATURE_SMAP)) {
next prev parent reply other threads:[~2015-11-17 14:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 9:31 [PATCH] x86/cpu: Fix SMAP check in PVOPS environments Andrew Cooper
2015-06-04 6:38 ` H. Peter Anvin
2015-06-04 8:58 ` Andrew Cooper
2015-06-04 19:55 ` Rusty Russell
2015-06-04 20:29 ` H. Peter Anvin
2015-06-05 2:58 ` Rusty Russell
2015-06-05 2:58 ` Rusty Russell
2015-06-05 7:13 ` Ingo Molnar
2015-06-05 7:13 ` Ingo Molnar
2015-06-05 9:33 ` [Xen-devel] " David Vrabel
2015-06-05 9:33 ` David Vrabel
2015-06-04 20:29 ` H. Peter Anvin
2015-06-04 19:55 ` Rusty Russell
2015-06-04 8:58 ` Andrew Cooper
2015-06-04 6:38 ` H. Peter Anvin
2015-11-17 14:59 ` Andrew Cooper
2015-11-17 14:59 ` Andrew Cooper [this message]
2015-11-19 10:12 ` [tip:x86/urgent] " tip-bot for Andrew Cooper
2015-11-19 10:12 ` tip-bot for Andrew Cooper
-- strict thread matches above, loose matches on Subject: below --
2015-06-03 9:31 [PATCH] " Andrew Cooper
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=564B40CC.4030304@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=lguest@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xen.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.