From: Peng Tao <bergwolf@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>, David Miller <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
kvm@vger.kernel.org, Jorgen Hansen <jhansen@vmware.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH v4 0/4] vsock: cancel connect packets when failing to connect
Date: Fri, 6 Jan 2017 10:22:56 +0800 [thread overview]
Message-ID: <CA+a=Yy7d940_OfNL=b_qZjnpRVL5pywKFpubtS_h6OtB7c2Dmg@mail.gmail.com> (raw)
In-Reply-To: <20161213095010.GA3103@stefanha-x1.localdomain>
On Tue, Dec 13, 2016 at 5:50 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Mon, Dec 12, 2016 at 08:21:05PM +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.
>>
>> v4 changelog:
>> - drop two unnecessary void * cast
>> - update new callback commnet
>> v3 changelog:
>> - define cancel_pkt callback in struct vsock_transport rather than struct virtio_transport
>> - rename virtio_vsock_pkt->vsk to virtio_vsock_pkt->cancel_token
>> v2 changelog:
>> - fix queued_replies counting and resume tx/rx when necessary
>>
>> Cheers,
>> Tao
>>
>> 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 | 41 ++++++++++++++++++++++++++++++++
>> include/linux/virtio_vsock.h | 2 ++
>> include/net/af_vsock.h | 3 +++
>> net/vmw_vsock/af_vsock.c | 14 +++++++++++
>> net/vmw_vsock/virtio_transport.c | 42 +++++++++++++++++++++++++++++++++
>> net/vmw_vsock/virtio_transport_common.c | 7 ++++++
>> 6 files changed, 109 insertions(+)
>>
>> --
>> 2.7.4
>>
>> _______________________________________________
>> Virtualization mailing list
>> Virtualization@lists.linux-foundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/virtualization
>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
ping~
It looks like the patchsets are reviewed but not merged. Is there any blocker?
Cheers,
Tao
next prev parent reply other threads:[~2017-01-06 2:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 12:21 [PATCH v4 0/4] vsock: cancel connect packets when failing to connect Peng Tao
2016-12-12 12:21 ` [PATCH v4 1/4] vsock: track pkt owner vsock Peng Tao
2016-12-12 12:21 ` [PATCH v4 2/4] vhost-vsock: add pkt cancel capability Peng Tao
2016-12-12 12:21 ` [PATCH v4 3/4] vsock: " Peng Tao
2016-12-12 12:21 ` [PATCH v4 4/4] vsock: cancel packets when failing to connect Peng Tao
2016-12-13 10:04 ` [PATCH v4 2/4] vhost-vsock: add pkt cancel capability Jorgen S. Hansen
2016-12-13 9:50 ` [PATCH v4 0/4] vsock: cancel connect packets when failing to connect Stefan Hajnoczi
2017-01-06 2:22 ` Peng Tao [this message]
2017-01-09 10:06 ` Stefan Hajnoczi
2017-01-17 9:25 ` Jorgen S. Hansen
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='CA+a=Yy7d940_OfNL=b_qZjnpRVL5pywKFpubtS_h6OtB7c2Dmg@mail.gmail.com' \
--to=bergwolf@gmail.com \
--cc=davem@davemloft.net \
--cc=jhansen@vmware.com \
--cc=kvm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stefanha@gmail.com \
--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).