Re: [PATCH] KVM: selftests: assert on exit reason in CR4/cpuid sync test

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Mar 20, 2019 at 11:50:26PM -0500, Wei Huang wrote:
> 
> 
> On 3/13/19 3:19 PM, Sean Christopherson wrote:
> > ...so that the test doesn't end up in an infinite loop if it fails for
> > whatever reason, e.g. SHUTDOWN due to gcc inserting stack canary code
> > into ucall() and attempting to derefence a null segment.
> 
> You fix passed on my box. Before I ack it, could you share the failure
> case (i.e. the steps to reproduce infinite loop) mentioned above?

Hit a triple fault shutdown due to derefencing an invalid fs: selector[1]
or because the addresses for the guest are borked[2].

[1] https://patchwork.kernel.org/patch/10851713/
[2] https://patchwork.kernel.org/patch/10851913/



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux