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

RE: [Xen-devel] [HVM] Corruption of buffered_io_page


  • To: "Trolle Selander" <trolle.selander@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Wed, 6 Dec 2006 22:05:27 -0000
  • Delivery-date: Wed, 06 Dec 2006 14:05:54 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AccZVUYfecSB869HQ9eYl7fIVO8qSQAAjY1w
  • Thread-topic: [Xen-devel] [HVM] Corruption of buffered_io_page

> read_pointer is the first member of buffered_ioreq_t, so on the hunch
that
> the corruption was occuring by something other than a wrong value
actually
> being written into the structure member, either overflowing a previous
> structure in memory or a pointer var mistake. I thus added a 64bit
dummy
> member to "pad" the buffered_ioreq_t structure at the start, and as I
had
> suspected, the bad value does get written into this dummy member
rather
> than the read_pointer. I haven't (yet) been able to track down what it
is
> that actually writes the bad value, and any help finding it would be
> welcome.

What compiler are you using? What guest OS? Are you using PV or emulated
drivers? Any idea if there are particular workloads that provoke the
problem?

Best,
Ian


_______________________________________________
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®.