提交 398d01b8 编写于 作者: D Daniel P. Berrange

Fix emission of domain events messages

The code which updated the message length after writing the
payload wrote the updated length word in the wrong place since
the XDR object was given a buffer pointing to the start of the
header payload, rather than message start.

* daemon/remote.c: Fix updating of event message length so that
  we actually send the payload, not just the header
上级 96ad9ed3
......@@ -4745,17 +4745,19 @@ remoteDispatchDomainEventSend (struct qemud_client *client,
/* Serialise the return header and event. */
xdrmem_create (&xdr,
msg->buffer + msg->bufferOffset,
msg->bufferLength - msg->bufferOffset,
msg->buffer,
msg->bufferLength,
XDR_ENCODE);
if (!xdr_remote_domain_event_msg(&xdr, data))
/* Skip over the header we just wrote */
if (xdr_setpos (&xdr, msg->bufferOffset) == 0)
goto xdr_error;
if (!xdr_remote_domain_event_msg(&xdr, data))
goto xdr_error;
/* Update length word */
msg->bufferOffset += xdr_getpos (&xdr);
len = msg->bufferOffset;
/* Update length word to include payload*/
len = msg->bufferOffset = xdr_getpos (&xdr);
if (xdr_setpos (&xdr, 0) == 0)
goto xdr_error;
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册