Paolo Bonzini <pbonzini@xxxxxxxxxx> writes:
> On 19/03/20 18:39, Sean Christopherson wrote:
>>> Yep. I worked through logic/math, mostly to gain a wee bit of knowledge
>>> about the clock stuff, and it's sound. The KVM_SET_CLOCK from syzkaller
>>> is simply making time go backwards.
>> Actually, would it make sense to return -EINVAL for KVM_SET_CLOCK if the
>> user tries to make kvmclock_offset go backwards?
>
> No, it is possible to do that depending on the clock setup on the live
> migration source. You could cause the warning anyway by setting the
> clock to a very high (signed) value so that kernel_ns + kvmclock_offset
> overflows.
If that overflow happens, then the original and the new host have an
uptime difference in the range of >200 hundreds of years. Very realistic
scenario...
Of course this can happen if you feed crap into the interface, but do
you really think that forwarding all crap to a guest is the right thing
to do?
As we all know the hypervisor orchestration stuff is perfect and would
never feed crap into the kernel which happily proliferates that crap to
the guest...
Seriously??
Thanks,
tglx
