From: Ingo Molnar <mingo@kernel.org>
To: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Brian Gerst <brgerst@gmail.com>,
Andy Lutomirski <luto@kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH urgent v2] x86, asm: Disable opportunistic SYSRET if regs->flags has TF set
Date: Thu, 2 Apr 2015 18:08:35 +0200 [thread overview]
Message-ID: <20150402160835.GC8045@gmail.com> (raw)
In-Reply-To: <551D64F0.4090208@redhat.com>
* Denys Vlasenko <dvlasenk@redhat.com> wrote:
> On 04/02/2015 02:59 PM, Denys Vlasenko wrote:
> > On 04/02/2015 02:31 PM, Ingo Molnar wrote:
> >> - we can optimize in a more directed fashion - like here
> >>
> >> ... while the downsides are:
> >>
> >> - more code
> >> - a (small) chance of a fix going to one path while not the other.
> >>
> >> How much extra code would it be?
> >
> > A screenful or two.
>
> I took a stab at it:
>
> text data bss dec hex filename
> 12530 0 0 12530 30f2 entry_64.o2
> 12562 0 0 12562 3112 entry_64.o
>
> The patch does two steps:
>
> (1) copy-pastes "retint_swapgs:" code into syscall handling code,
> the copy is under "syscall_return:" label.
>
> (2) remove "opportunistic sysret" code from "retint_swapgs" code block,
> since now it won't be reached by syscall return. This in fact removes
> most of the code in question.
>
> Lightly run-tested so far.
>
> Ingo, do you want this in a proper patch form?
Yeah, that looks good to me (only lightly reviewed).
Thanks,
Ingo
next prev parent reply other threads:[~2015-04-02 16:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 21:26 [PATCH urgent v2] x86, asm: Disable opportunistic SYSRET if regs->flags has TF set Andy Lutomirski
2015-04-02 6:21 ` Borislav Petkov
2015-04-02 9:07 ` Ingo Molnar
2015-04-02 10:07 ` Denys Vlasenko
2015-04-02 10:37 ` Ingo Molnar
2015-04-02 11:14 ` Brian Gerst
2015-04-02 12:24 ` Denys Vlasenko
2015-04-02 12:31 ` Ingo Molnar
2015-04-02 12:59 ` Denys Vlasenko
2015-04-02 15:49 ` Denys Vlasenko
2015-04-02 16:08 ` Ingo Molnar [this message]
2015-04-02 14:26 ` Andy Lutomirski
2015-04-02 12:32 ` [tip:x86/urgent] x86/asm/entry/64: " tip-bot for Andy Lutomirski
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=20150402160835.GC8045@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=torvalds@linux-foundation.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 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.