| commit | a3feb08639e7982f47c3981fea79d527d3dfc0ac | |
| author | Markus Armbruster <armbru@redhat.com> | |
| Tue, 15 Mar 2016 18:34:42 +0000 (15 19:34 +0100) | ||
| committer | Markus Armbruster <armbru@redhat.com> | |
| Mon, 21 Mar 2016 20:29:01 +0000 (21 21:29 +0100) | ||
| tree | 5e338783bfe45a06993b1aa14a62545f09dffdd4 | treesnapshot (tar.gz zip) |
| parent | 1309cf448a6d88d8a693c15d5b11ad07af2321ab | commitdiff |
ivshmem: Rely on server sending the ID right after the version
The protocol specification (ivshmem-spec.txt, formerly
ivshmem_device_spec.txt) has always required the ID message to be sent
right at the beginning, and ivshmem-server has always complied. The
device, however, accepts it out of order. If an interrupt setup
arrived before it, though, it would be misinterpreted as connect
notification. Fix the latent bug by relying on the spec and
ivshmem-server's actual behavior.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <1458066895-20632-28-git-send-email-armbru@redhat.com>
The protocol specification (ivshmem-spec.txt, formerly
ivshmem_device_spec.txt) has always required the ID message to be sent
right at the beginning, and ivshmem-server has always complied. The
device, however, accepts it out of order. If an interrupt setup
arrived before it, though, it would be misinterpreted as connect
notification. Fix the latent bug by relying on the spec and
ivshmem-server's actual behavior.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <1458066895-20632-28-git-send-email-armbru@redhat.com>
| hw/misc/ivshmem.c | diffblobblamehistory |