| commit | a3f2fa6592b11968018596765217a1f780c1fde5 | |
| author | Hans de Goede <hdegoede@redhat.com> | |
| Wed, 23 Mar 2011 19:18:21 +0000 (23 20:18 +0100) | ||
| committer | Hans de Goede <hdegoede@redhat.com> | |
| Wed, 23 Mar 2011 19:22:17 +0000 (23 20:22 +0100) | ||
| tree | ee403165479aac8185e90f29cbce8a70274c0fb9 | treesnapshot (tar.gz zip) |
| parent | bddc471e1b43e8f30f52e8bd9054f145a19206af | commitdiff |
vdagent-virtio-port: properly demultiplex vdagent messages per port
Before this patch vdagent-virtio-port was assembling vdagent messages
which consist of multiple chunks without looking at the chunk header port
attribute. But it is possible to receive a vdagent-message which spans
multiple chunks for port 1, and while receiving the chunks for this message,
receive an unrelated chunk for port 2. Before this patch that chunk would
(wrongly) get added to the message for port2, messing things seriously up.
Before this patch vdagent-virtio-port was assembling vdagent messages
which consist of multiple chunks without looking at the chunk header port
attribute. But it is possible to receive a vdagent-message which spans
multiple chunks for port 1, and while receiving the chunks for this message,
receive an unrelated chunk for port 2. Before this patch that chunk would
(wrongly) get added to the message for port2, messing things seriously up.
| vdagent-virtio-port.c | diffblobblamehistory |