From: Juergen Gross <jgross@suse.com>
To: Andy Lutomirski <luto@kernel.org>, x86@kernel.org
Cc: linux-kernel@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
Brian Gerst <brgerst@gmail.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH PTI] Fixup "x86/entry/64: Use a per-CPU trampoline stack for IDT entries"
Date: Wed, 6 Dec 2017 09:24:36 +0100 [thread overview]
Message-ID: <810a4628-6d5e-44bf-e7e8-f7e6c8dc876a@suse.com> (raw)
In-Reply-To: <5f8c2b0655ce0575c1e5820d9620e645ccc0ea4c.1512539981.git.luto@kernel.org>
On 06/12/17 07:00, Andy Lutomirski wrote:
> Add to commit message:
>
> Using a trampoline stack would obnoxious for Xen PV because Xen PV
> enters entry_SYSCALL_64_after_hwframe on the stack indicated by sp0.
> This could be fixed, but I think it's nice to ensure the entry code
> can still work without a trampoline stack. So this patch doesn't
> use the entry trampoline stack on Xen.
>
> The regs != eregs check in sync_regs is optional, but I think it's
> better than copying the whole set of regs over itself.
>
> Signed-off-by: Andy Lutomirski <luto@kernel.org>
I verified the crash occurring without the patch when started as a
pv guest.
Your patch makes pv guest boot again. HVM guest is working, too.
You can add my:
Tested-by: Juergen Gross <jgross@suse.com>
Juergen
> ---
>
> Boris, this is lightly tested and should fix the problem you're seeing.
>
> arch/x86/include/asm/switch_to.h | 3 +++
> arch/x86/kernel/traps.c | 9 +++++----
> 2 files changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/include/asm/switch_to.h b/arch/x86/include/asm/switch_to.h
> index fab453ad2460..cbc71e73bd32 100644
> --- a/arch/x86/include/asm/switch_to.h
> +++ b/arch/x86/include/asm/switch_to.h
> @@ -93,6 +93,9 @@ static inline void update_sp0(struct task_struct *task)
> /* On x86_64, sp0 always points to the entry trampoline stack, which is constant: */
> #ifdef CONFIG_X86_32
> load_sp0(task->thread.sp0);
> +#else
> + if (static_cpu_has(X86_FEATURE_XENPV))
> + load_sp0(task_top_of_stack(task));
> #endif
> }
>
> diff --git a/arch/x86/kernel/traps.c b/arch/x86/kernel/traps.c
> index 40cc3dc5967a..ee9ca0ad4388 100644
> --- a/arch/x86/kernel/traps.c
> +++ b/arch/x86/kernel/traps.c
> @@ -619,14 +619,15 @@ NOKPROBE_SYMBOL(do_int3);
>
> #ifdef CONFIG_X86_64
> /*
> - * Help handler running on IST stack to switch off the IST stack if the
> - * interrupted code was in user mode. The actual stack switch is done in
> - * entry_64.S
> + * Help handler running on a per-cpu (IST or entry trampoline) stack
> + * to switch to the normal thread stack if the interrupted code was in
> + * user mode. The actual stack switch is done in entry_64.S
> */
> asmlinkage __visible notrace struct pt_regs *sync_regs(struct pt_regs *eregs)
> {
> struct pt_regs *regs = (struct pt_regs *)this_cpu_read(cpu_current_top_of_stack) - 1;
> - *regs = *eregs;
> + if (regs != eregs)
> + *regs = *eregs;
> return regs;
> }
> NOKPROBE_SYMBOL(sync_regs);
>
prev parent reply other threads:[~2017-12-06 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 6:00 Andy Lutomirski
2017-12-06 8:24 ` Juergen Gross [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=810a4628-6d5e-44bf-e7e8-f7e6c8dc876a@suse.com \
--to=jgross@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=x86@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
all inboxes | Powered by JetHome®