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

[Xen-devel] [HVM] Some ASSERT()s in vlapic.c should be removed and the cases should be handled more carefully?


  • To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
  • Date: Fri, 14 Dec 2007 13:48:41 +0800
  • Delivery-date: Thu, 13 Dec 2007 21:50:00 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acg+FPS0YfTg/FAHQQ+dkKlAAN74dw==
  • Thread-topic: [HVM] Some ASSERT()s in vlapic.c should be removed and the cases should be handled more carefully?

For the ASSERT()s in vlapic_find_highest_irr(), vlapic_read(), if we are
using a debug=y build Xen, a malicious guest kernel or module can send a
vIPI with vector less than 16, or read a non-aligned address -- then the
ASSERT can crash Xen.

For the valid vector, maybe we should add the  emulation of
APIC_ESR(Error Status Register).

-- Dexuan

 


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.