On 08/16/2011 05:25 PM, Daniel P. Berrange wrote:
From: "Daniel P. Berrange"<[email protected]>

If a client had initiated a stream abort, it will have a call
waiting for a reply in the queue. If more data continues to
arrive on the stream, the abort command could mistakenly get
signalled as complete. Remove the code from async data processing
that looked for waiting calls. Add a sanity check to ensure no
async call can ever be marked as needing a reply

* src/rpc/virnetclient.c: Ensure async data packets can't
   trigger a reply
---
  src/rpc/virnetclient.c |   12 +++++++-----
  1 files changed, 7 insertions(+), 5 deletions(-)

ACK.

--
Eric Blake   [email protected]    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

--
libvir-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/libvir-list

Reply via email to