Received-SPF: pass (google.com: domain of linux-kernel+bounces-175919-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Precedence: bulk
MIME-Version: 1.0
References: <20240423165328.2853870-1-seanjc@google.com>
In-Reply-To: <20240423165328.2853870-1-seanjc@google.com>
From: Paolo Bonzini <pbonzini@redhat.com>
Date: Fri, 10 May 2024 16:50:24 +0200
Message-ID: <CABgObfYYm_xwEFjNx0jzaVg2R6s1D5EWC2T6Fx-d++8=6nvm1g@mail.gmail.com>
Subject: Re: [PATCH 0/3] KVM: x86: Fix supported VM_TYPES caps
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 23, 2024 at 6:53=E2=80=AFPM Sean Christopherson <seanjc@google.=
com> wrote:
>
> Fix a goof where KVM fails to re-initialize the set of supported VM types=
,
> resulting in KVM overreporting the set of supported types when a vendor
> module is reloaded with incompatible settings.  E.g. unload kvm-intel.ko,
> reload with ept=3D0, and KVM will incorrectly treat SW_PROTECTED_VM as
> supported.
>
> Fix a similar long-standing bug with supported_mce_cap that is much less
> benign, and then harden against us making the same mistake in the future.
>
> Sean Christopherson (3):
>   KVM: x86: Fully re-initialize supported_vm_types on vendor module load
>   KVM: x86: Fully re-initialize supported_mce_cap on vendor module load
>   KVM: x86: Explicitly zero kvm_caps during vendor module load

Applied, thanks.

Paolo