From: Jim Mattson <jmattson@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: nVMX: Fix memory corruption when using VMCS shadowing
Date: Fri, 1 Jul 2016 09:17:03 -0700 [thread overview]
Message-ID: <CALMp9eTK_xcVeHAH+zLF0FRUCgmo_yNsEBZta56ZBgLLxq81TQ@mail.gmail.com> (raw)
In-Reply-To: <9e137134-8c82-48bc-9899-49cdbc205384@redhat.com>
I agree. I'll have a revised proposal next week.
On Fri, Jul 1, 2016 at 5:33 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
>
> On 01/07/2016 07:24, Paolo Bonzini wrote:
>> So perhaps it's the callers of nested_release_vmcs12 that have to ensure
>> vcpu_load/vcpu_put are called if necessary around the calls to
>> nested_release_vmcs12. Only free_nested should need this. The other
>> callers of nested_release_vmcs12 and copy_shadow_to_vmcs12 are vmexit
>> handlers and do have the problem.
>
> ... do not have.
>
> Paolo
next prev parent reply other threads:[~2016-07-01 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 22:24 [PATCH] KVM: nVMX: Fix memory corruption when using VMCS shadowing Jim Mattson
2016-07-01 5:24 ` Paolo Bonzini
2016-07-01 12:33 ` Paolo Bonzini
2016-07-01 16:17 ` Jim Mattson [this message]
2016-07-08 22:36 ` [PATCH v2] " Jim Mattson
2016-07-09 5:59 ` Paolo Bonzini
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=CALMp9eTK_xcVeHAH+zLF0FRUCgmo_yNsEBZta56ZBgLLxq81TQ@mail.gmail.com \
--to=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
/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.