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

[Xen-devel] xenstore ring overflow when too many watches are fired

  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Thu, 8 Oct 2009 22:01:25 +1100
  • Delivery-date: Thu, 08 Oct 2009 04:01:49 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcpIBq1xI/hXC2nOST2UVLFiVzrk3A==
  • Thread-topic: xenstore ring overflow when too many watches are fired

A bug has been discovered in GPLPV that causes duplicate watches to be
added when Windows resumes from a hibernate. I'm not completely sure at
this point, but it appears that the firing of that many watches causes
dom0 to overwrite data on the ring.

Are there any protections in xenstored (which does the writing I think)
against xenstore ring overflow caused by a large number (>23 I think) of
watches firing in unison? I can't see any...

Obviously I'll fix the GPLPV bug too, but it would be nice to know that
too many watches wouldn't break xenstore.



Xen-devel mailing list



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