On Wed, Mar 15, 2017 at 09:32:13AM +0800, Peng Tao wrote:
Currently, if a connect call fails on a signal or timeout (e.g., guest is still
in the process of starting up), we'll just return to caller and leave the connect
packet queued and they are sent even though the connection is considered a failure,
which can confuse applications with unwanted false connect attempt.
The patchset enables vsock (both host and guest) to cancel queued packets when
a connect attempt is considered to fail.
v5 changelog:
- change virtio_vsock_pkt->cancel_token back to virtio_vsock_pkt->vsk
As discussed previously, it's an opaque token that is not interpreted or
dereferenced. A unique integer could be used instead of the pointer we
conveniently use as the token today. I still think it should be void *
or uintptr_t, but let's move on.
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>