Re: [PATCH v2 2/3] KVM: nVMX: Ack and write vector info to intr_info if L1 asks us to

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

 



Il 11/04/2014 15:20, Marcelo Tosatti ha scritto:
> >
> > Can irq be -1 ?
>
> If it is, I think that's a bug because if we exited for this
> reason with INTR_ACK set, the hypervisor expects a valid vector
> number to be available.
>
> What about adding a BUG_ON ?
Sounds good.

Each BUG_ON we add to KVM is a potential guest-kill-host vulnerability. WARN_ON is better.

Paolo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[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