Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH] KVM: SVM: delay svm_vcpu_init_msrpm after svm->vmcb is
 initialized
To:     Paolo Bonzini <pbonzini@redhat.com>
Cc:     Dan Carpenter <dan.carpenter@oracle.com>,
        linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
        Vitaly Kuznetsov <vkuznets@redhat.com>
References: <20210726165843.1441132-1-pbonzini@redhat.com>
 <87zgu76ary.fsf@vitty.brq.redhat.com>
From:   Vineeth Pillai <viremana@linux.microsoft.com>
Message-ID: <1d82501c-05fd-deff-9652-790cde052644@linux.microsoft.com>
Date:   Wed, 28 Jul 2021 16:18:21 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <87zgu76ary.fsf@vitty.brq.redhat.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Precedence: bulk


On 7/27/2021 11:23 AM, Vitaly Kuznetsov wrote:
> Paolo Bonzini <pbonzini@redhat.com> writes:
>
>> Right now, svm_hv_vmcb_dirty_nested_enlightenments has an incorrect
>> dereference of vmcb->control.reserved_sw before the vmcb is checked
>> for being non-NULL.  The compiler is usually sinking the dereference
>> after the check; instead of doing this ourselves in the source,
>> ensure that svm_hv_vmcb_dirty_nested_enlightenments is only called
>> with a non-NULL VMCB.
>>
>> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
>> Cc: Vineeth Pillai <viremana@linux.microsoft.com>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> [Untested for now due to issues with my AMD machine. - Paolo]
Finally got hold of an AMD machine and tested nested virt: windows on 
linux on
windows with the patches applied. Did basic boot and minimal verification.

Tested-by: Vineeth Pillai <viremana@linux.microsoft.com>

Thanks,
Vineeth