This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 515] vif-script called after domain is destroyed

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 515] vif-script called after domain is destroyed
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 22 Mar 2006 19:19:01 +0000
Delivery-date: Wed, 22 Mar 2006 19:21:30 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

------- Additional Comments From harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx  
2006-03-22 19:19 -------
I recreated this on changeset 5032ee221f75 using 64 bit ubuntu from which I
removed udev and configured hotplug such that /proc/sys/kernel/hotplug showed
/sbin/hotplug rather than /sbin/udevsend.

The problem is that the hotplug call for vif-route offline is followed closely
by the hotplug call for xen-hotplug-cleanup and the two scripts execute

The xen-hotplug-cleanup script removes the device details from the store before
the vif-route script completes so there is a window where it is possible for the
vif-route to try to read details from the store and fail to find them.

I put some syslog messages in the scripts which confirmed that this was 

The reason the problem is only evident when udev is removed is probably that
/sbin/udevsend is designed to serialise hotplug events to avoid exactly this
kind of problem.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>