From: Bandan Das <bsd@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: KVM: nSVM: Check for NRIPS support before updating control field
Date: Mon, 29 Jun 2015 16:22:42 -0400 [thread overview]
Message-ID: <jpgwpym463x.fsf@redhat.com> (raw)
In-Reply-To: <20150629192810.GA19965@kroah.com> (Greg KH's message of "Mon, 29 Jun 2015 12:28:10 -0700")
Greg KH <gregkh@linuxfoundation.org> writes:
> On Mon, Jun 29, 2015 at 03:18:51PM -0400, Bandan Das wrote:
>>
>> Commit f104765b4f81fd74d69e0eb161e89096deade2db upstream.
>>
>> This causes the L1 guest to crash when running a nested guest
>> with an AMD processor that doesn't support NRIPS.
>>
>> If hardware doesn't support DecodeAssist - a feature that provides
>> more information about the intercept in the VMCB, KVM decodes the
>> instruction and then updates the next_rip vmcb control field.
>> However, NRIP support itself depends on cpuid Fn8000_000A_EDX[NRIPS].
>> Since skip_emulated_instruction() doesn't verify nrip support
>> before accepting control.next_rip as valid, avoid writing this
>> field if support isn't present.
>>
>> Signed-off-by: Bandan Das <bsd@redhat.com>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>> arch/x86/kvm/svm.c | 8 ++++++--
>> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> What stable kernel trees do you want this applied to?
Sorry, I missed that part. I believe this bug is present
since commit cfec82cb7d3 which makes it applicable to
#3.0+
Bandan
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2015-06-29 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 19:18 KVM: nSVM: Check for NRIPS support before updating control field Bandan Das
2015-06-29 19:28 ` Greg KH
2015-06-29 20:22 ` Bandan Das [this message]
2015-07-01 9:23 ` Luis Henriques
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=jpgwpym463x.fsf@redhat.com \
--to=bsd@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=pbonzini@redhat.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 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.