On Wed, 24 Apr 2019, Fenghua Yu wrote:
>
> +static void atomic_switch_msr_test_ctl(struct vcpu_vmx *vmx)
> +{
> + u64 host_msr_test_ctl;
> +
> + if (!boot_cpu_has(X86_FEATURE_SPLIT_LOCK_DETECT))
> + return;
Again: MSR_TST_CTL is not only about LOCK_DETECT. Check the control mask.
> + host_msr_test_ctl = this_cpu_read(msr_test_ctl_cache);
> +
> + if (host_msr_test_ctl == vmx->msr_test_ctl) {
This still assumes that the only bit which can be set in the MSR is that
lock detect bit.
> + clear_atomic_switch_msr(vmx, MSR_TEST_CTL);
> + } else {
> + add_atomic_switch_msr(vmx, MSR_TEST_CTL, vmx->msr_test_ctl,
> + host_msr_test_ctl, false);
So what happens here is that if any other bit is set on the host, VMENTER
will happily clear it.
guest = (host & ~vmx->test_ctl_mask) | vmx->test_ctl;
That preserves any bits which are not exposed to the guest.
But the way more interesting question is why are you exposing the MSR and
the bit to the guest at all if the host has split lock detection enabled?
That does not make any sense as you basically allow the guest to switch it
off and then launch a slowdown attack. If the host has it enabled, then a
guest has to be treated like any other process and the #AC trap has to be
caught by the hypervisor which then kills the guest.
Only if the host has split lock detection disabled, then you can expose it
and allow the guest to turn it on and handle it on its own.
Thanks,
tglx
