Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Luis Henriques <luis.henriques@canonical.com>
To: Kamal Mostafa <kamal@canonical.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sasha.levin@oracle.com>, Jiri Slaby <jslaby@suse.cz>,
	stable@vger.kernel.org, Andy Lutomirski <luto@kernel.org>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [3.xx-stable backport] x86/entry/compat: Add missing CLAC to entry_INT80_32
Date: Mon, 7 Mar 2016 10:17:38 +0000	[thread overview]
Message-ID: <20160307101738.GA3081@ares> (raw)
In-Reply-To: <1457117182-27061-1-git-send-email-kamal@canonical.com>

On Fri, Mar 04, 2016 at 10:46:22AM -0800, Kamal Mostafa wrote:
> From: Andy Lutomirski <luto@kernel.org>
> 
> commit 3d44d51bd339766f0178f0cf2e8d048b4a4872aa upstream.
> 
> This doesn't seem to fix a regression -- I don't think the CLAC was
> ever there.
> 
> I double-checked in a debugger: entries through the int80 gate do
> not automatically clear AC.
> 
> Stable maintainers: I can provide a backport to 4.3 and earlier if
> needed.  This needs to be backported all the way to 3.10.
> 
> Reported-by: Brian Gerst <brgerst@gmail.com>
> Signed-off-by: Andy Lutomirski <luto@kernel.org>
> Cc: Andy Lutomirski <luto@amacapital.net>
> Cc: Borislav Petkov <bp@alien8.de>
> Cc: Denys Vlasenko <dvlasenk@redhat.com>
> Cc: H. Peter Anvin <hpa@zytor.com>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: <stable@vger.kernel.org> # v3.10 and later
> Fixes: 63bcff2a307b ("x86, smap: Add STAC and CLAC instructions to control user space access")
> Link: http://lkml.kernel.org/r/b02b7e71ae54074be01fc171cbd4b72517055c0e.1456345086.git.luto@kernel.org
> Signed-off-by: Ingo Molnar <mingo@kernel.org>
> [ kamal: backport to 3.10 through 3.19-stable: file rename; context ]

Thanks Kamal, I'll queue it for the 3.16 kernel.

Cheers,
--
Lu�s

> Signed-off-by: Kamal Mostafa <kamal@canonical.com>
> ---
>  arch/x86/ia32/ia32entry.S | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/x86/ia32/ia32entry.S b/arch/x86/ia32/ia32entry.S
> index 82e8a1d..164f541 100644
> --- a/arch/x86/ia32/ia32entry.S
> +++ b/arch/x86/ia32/ia32entry.S
> @@ -422,6 +422,7 @@ ENTRY(ia32_syscall)
>  	/*CFI_REL_OFFSET	cs,CS-RIP*/
>  	CFI_REL_OFFSET	rip,RIP-RIP
>  	PARAVIRT_ADJUST_EXCEPTION_FRAME
> +	ASM_CLAC			/* Do this early to minimize exposure */
>  	SWAPGS
>  	/*
>  	 * No need to follow this irqs on/off section: the syscall
> -- 
> 2.7.0
> 
> --
> To unsubscribe from this list: send the line "unsubscribe stable" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2016-03-07 10:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 20:18 [PATCH] x86/entry/compat: Add missing CLAC to entry_INT80_32 Andy Lutomirski
2016-03-04 18:46 ` [3.xx-stable backport] " Kamal Mostafa
2016-03-04 22:21   ` Andy Lutomirski
2016-03-05 18:52     ` Greg Kroah-Hartman
2016-03-07 10:17   ` Luis Henriques [this message]

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=20160307101738.GA3081@ares \
    --to=luis.henriques@canonical.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=kamal@canonical.com \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=sasha.levin@oracle.com \
    --cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox