>>> On 12.06.16 at 16:09, <wei.l...@citrix.com> wrote:
> --- a/tools/libxl/libxl.c
> +++ b/tools/libxl/libxl.c
> @@ -4927,10 +4927,12 @@ retry_transaction:
>
> target = libxl__xs_read(gc, t, GCSPRINTF("%s/memory/target", dompath));
> if (!target && !domid) {
> - if (!xs_transaction_end(ctx->xsh, t, 1))
> + if (!xs_transaction_end(ctx->xsh, t, 1)) {
> + rc = ERROR_FAIL;
I'm sorry for noticing this only now - is ERROR_FAIL the right thing
to use here, considering how things worked before the change that
introduced the issue getting fixed here? I had intentionally decided
to use ERROR_INVAL in the patch variant I did submit (as at that
time I wasn't yet aware of the other fix floating around already).
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
