[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Xenstore remove problem - causes bug #473
On Tuesday 10 January 2006 12:19, Keir Fraser wrote: > Perhaps something is watching vif/1 and, when the watch fires, > erroneously causing all vif/1* to get deleted? > I found it! When a change occur on one backend device we call cleanup_devices() for each device in bus. The problem is: the test to see if that device was changed is being done with strncmp(), using the length of the changed node as maximum length to be compared. I think the idea is that any sub-node should be matched also, like: if "backend/1/status" changed we have to call backend_changed to "backend/1" device, and that is ok. But with that code If we delete device "backend/1" all devices matching "backend/1*" are being deleted also. Suggestions on the best/prettier way to handle that? -- Murillo Fernandes Bernardes IBM Linux Technology Center _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |