disable OACR to prevent it leaving locks in the build tree
Merge pull request #11 from dickon/master

disable OACR to prevent it leaving locks in the build tree
Fix xenbus to cause surprise removals for vusb device on removal.

The Windows front end vusb driver expects to be removed via a
surprise removal. The existing code was trying to do an eject
which was not causing the front end driver to finish cleaning up
the device that was removed. Custom code for surprise removal was
only added for vusb devices to prevent injuring the already delicate
shutdown/removal code for other types of devices.

OXT-35

Signed-off-by: Ross Philipson ross.philipson@gmail.com
Fix xenbus to not re-enumerate closed VUSB devices.

When VUSB devices are removed, they are just gone for good. There
is no possibility of a reconnect. This fix detects the backend state
went to closed which means the device was there and gone. In this
case, xenbus just ignores the closed device. The usbowls thingy can
then properly clean up the mess in xenstore.

OXT-35

Signed-off-by: Ross Philipson ross.philipson@gmail.com
VUSB moved reconnect check one block out.

OXT-35

Signed-off-by: Ross Philipson <ross.philipson@gmail.com>
Merge pull request #12 from rossphilipson/master

Fix xenbus to cause surprise removals for vusb device on removal.
Use a more generic and reliable scheme to do surprise removals.

The first version relied on the backend device going to state=closed
which is generally ok. In cases like surprise removal during sleep
this does not work as well. It is better to use an explicit flag
to indicate the state of the device.

OXT-61

Signed-off-by: Ross Philipson <ross.philipson@gmail.com>
Merge pull request #13 from rossphilipson/xenbus_surprise_remove

Use a more generic and reliable scheme to do surprise removals.
Fix xen bus device reference count handling to prevent leaks.

This is a somewhat minimal attempt to fix the xen device reference
counting. There are a number of comments in the code to give an idea
of what is going on. The exhaustion of resources seen while testing
vusb device plug/unplug was caused by improper reference counting
leading to leaked memory and xenbus resources. This also fixes the
same leaks when vif/vwif devices are disconnected and connected.

OXT-70

Signed-of-by: Ross Philipson <ross.philipson@gmail.com>
Merge pull request #14 from rossphilipson/xenbus_fix_device_deref

Fix xen bus device reference count handling to prevent leaks.