From: Peng Tao <bergwolf@gmail.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, Peng Tao <bergwolf@gmail.com>
Subject: [PATCH 0/4] vsock: cancel connect packets when failing to connect
Date: Wed, 7 Dec 2016 18:00:17 +0800 [thread overview]
Message-ID: <1481104821-77294-1-git-send-email-bergwolf@gmail.com> (raw)
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.
Peng Tao (4):
vsock: track pkt owner vsock
vhost-vsock: add pkt cancel capability
vsock: add pkt cancel capability
vsock: cancel packets when failing to connect
drivers/vhost/vsock.c | 29 ++++++++++++++++++++++++++
include/linux/virtio_vsock.h | 12 +++++++++++
net/vmw_vsock/af_vsock.c | 7 +++++++
net/vmw_vsock/virtio_transport.c | 36 +++++++++++++++++++++++++++++++++
net/vmw_vsock/virtio_transport_common.c | 14 ++++++-------
5 files changed, 91 insertions(+), 7 deletions(-)
--
2.7.4
next reply other threads:[~2016-12-07 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 10:00 Peng Tao [this message]
2016-12-07 10:00 ` [PATCH 1/4] vsock: track pkt owner vsock Peng Tao
2016-12-07 10:00 ` [PATCH 2/4] vhost-vsock: add pkt cancel capability Peng Tao
2016-12-07 13:23 ` Stefan Hajnoczi
2016-12-07 10:00 ` [PATCH 3/4] vsock: " Peng Tao
2016-12-07 13:22 ` Stefan Hajnoczi
2016-12-07 14:46 ` Peng Tao
2016-12-07 10:00 ` [PATCH 4/4] vsock: cancel packets when failing to connect Peng Tao
2016-12-07 13:25 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1481104821-77294-1-git-send-email-bergwolf@gmail.com \
--to=bergwolf@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).