From: Josh Poimboeuf <jpoimboe@kernel.org>
To: Jon Kohler <jon@nutanix.com>
Cc: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
X86 ML <x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Daniel Sneddon <daniel.sneddon@linux.intel.com>,
"kvm @ vger . kernel . org" <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [PATCH] KVM: VMX: remove LFENCE in vmx_spec_ctrl_restore_host()
Date: Wed, 31 May 2023 17:42:02 -0700 [thread overview]
Message-ID: <20230601004202.63yulqs73kuh3ep6@treble> (raw)
In-Reply-To: <F4BEBCAF-CBFC-4C3E-8B01-2ED84CF2E13A@nutanix.com>
On Wed, May 31, 2023 at 11:58:12PM +0000, Jon Kohler wrote:
> > The goal of this barrier_nospec() is to prevent speculative execution
> > from bypassing the SPEC_CTRL write (due to misprediction of the
> > conditional branch, Spectre v1 style). Otherwise the next indirect
> > branch or unbalanced RET could be an attack target.
> >
> > So any previous LFENCEs before that conditional branch won't help here.
>
> Ah interesting. Ok, to be clear, thats a guest -> host attack, correct? And such
> an attack would not at all be thwarted by the first CALL retire + LFENCE that
> was added on commit 2b1299322016 ("x86/speculation: Add RSB VM Exit
> protections”)?
Right.
> Sorry to be long winded, just wanting to triple check because
> the aforementioned commit was added slightly after the original one, and I
> want to make extra sure that they aren’t solving the same thing.
>
> If that is indeed the case, does that commit need to be revisited at all?
>
> Or are we saying that this Intel vulnerability needs *two* LFENCE’s to keep
> the host secure?
The first LFENCE (FILL_RETURN_BUFFER) forces the CALL to retire so the
RSB stuff is guaranteed to take effect before the next unbalanced RET
can be speculatively executed.
The second LFENCE (vmx_spec_ctrl_restore_host) forces the conditional
branch to retire so the SPEC_CTRL write (potential IBRS/eIBRS
enablement) is guaranteed to take effect before the next indirect branch
and/or unbalanced RET can be speculatively executed.
So each LFENCE has a distinct purpose. That said, there are no indirect
branches or unbalanced RETs between them. So it should be fine to
combine them into a single LFENCE after both.
You could for example just remove the first LFENCE. But only for that
usage site, i.e. not for other users of FILL_RETURN_BUFFER.
Or, remove them both and add an LFENCE in vmx_vmexit() right after the
call to vmx_spec_ctrl_restore_host(). That might be clearer. Then it
could have a comment describing its dual purposes.
--
Josh
next prev parent reply other threads:[~2023-06-01 0:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 15:01 [PATCH] KVM: VMX: remove LFENCE in vmx_spec_ctrl_restore_host() Jon Kohler
2023-05-31 23:18 ` Josh Poimboeuf
2023-05-31 23:58 ` Jon Kohler
2023-06-01 0:42 ` Josh Poimboeuf [this message]
2023-06-01 0:50 ` Andrew Cooper
2023-06-01 0:56 ` Josh Poimboeuf
2023-06-01 1:24 ` Pawan Gupta
2023-06-01 4:23 ` Josh Poimboeuf
2023-06-05 14:29 ` Jon Kohler
2023-06-05 16:35 ` Josh Poimboeuf
2023-06-05 16:39 ` Jon Kohler
2023-06-05 17:31 ` Pawan Gupta
2023-06-05 18:31 ` Sean Christopherson
2023-06-05 19:57 ` Jon Kohler
2023-06-05 20:01 ` Josh Poimboeuf
2023-06-06 0:20 ` Andrew Cooper
2023-06-06 3:59 ` Josh Poimboeuf
2023-06-01 0:29 ` Andrew Cooper
2023-06-01 0:53 ` Josh Poimboeuf
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=20230601004202.63yulqs73kuh3ep6@treble \
--to=jpoimboe@kernel.org \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=daniel.sneddon@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jon@nutanix.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--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