On Thu, Apr 14, Juergen Gross wrote: > On 13/04/16 10:56, Olaf Hering wrote: > > + back = flexarray_make(gc, i, 1); > Shouldn't be this in the loop below? Otherwise the array might be > expanded with the same entries several times in case of a transaction > collision.
I think the result would be like 'echo val > path ; echo val > path'. But in theory one iteration could enter XenbusStateConnected, and a following one another state. In practice this would be XenbusStateReconfiguring and the loop is done. What would be the way to free a flexarray? Looks like flexarray_free would lead to a double free if the gc itself is finally freed. Just overwriting 'back' would work, but does Coverity understand that the previous back is not leaked? Olaf _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
