From: patchwork-bot+netdevbpf@kernel.org
To: None <f.storniolo95@gmail.com>
Cc: luigi.leonardi@outlook.com, kvm@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, mst@redhat.com,
imbrenda@linux.vnet.ibm.com, kuba@kernel.org, asias@redhat.com,
stefanha@redhat.com, pabeni@redhat.com, sgarzare@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH net 0/4] vsock: fix server prevents clients from reconnecting
Date: Tue, 07 Nov 2023 22:30:25 +0000 [thread overview]
Message-ID: <169939622521.29953.960000418979346249.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231103175551.41025-1-f.storniolo95@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 3 Nov 2023 18:55:47 +0100 you wrote:
> From: Filippo Storniolo <f.storniolo95@gmail.com>
>
> This patch series introduce fix and tests for the following vsock bug:
> If the same remote peer, using the same port, tries to connect
> to a server on a listening port more than once, the server will
> reject the connection, causing a "connection reset by peer"
> error on the remote peer. This is due to the presence of a
> dangling socket from a previous connection in both the connected
> and bound socket lists.
> The inconsistency of the above lists only occurs when the remote
> peer disconnects and the server remains active.
> This bug does not occur when the server socket is closed.
>
> [...]
Here is the summary with links:
- [net,1/4] vsock/virtio: remove socket from connected/bound list on shutdown
https://git.kernel.org/netdev/net/c/3a5cc90a4d17
- [net,2/4] test/vsock fix: add missing check on socket creation
https://git.kernel.org/netdev/net/c/bfada5a7672f
- [net,3/4] test/vsock: refactor vsock_accept
https://git.kernel.org/netdev/net/c/84d5fb974131
- [net,4/4] test/vsock: add dobule bind connect test
https://git.kernel.org/netdev/net/c/d80f63f69025
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-11-07 22:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 17:55 [PATCH net 0/4] vsock: fix server prevents clients from reconnecting f.storniolo95
2023-11-03 17:55 ` [PATCH net 1/4] vsock/virtio: remove socket from connected/bound list on shutdown f.storniolo95
2023-11-06 10:43 ` Stefano Garzarella
2023-11-03 17:55 ` [PATCH net 2/4] test/vsock fix: add missing check on socket creation f.storniolo95
2023-11-06 10:46 ` Stefano Garzarella
2023-11-03 17:55 ` [PATCH net 3/4] test/vsock: refactor vsock_accept f.storniolo95
2023-11-06 10:47 ` Stefano Garzarella
2023-11-03 17:55 ` [PATCH net 4/4] test/vsock: add dobule bind connect test f.storniolo95
2023-11-06 10:48 ` Stefano Garzarella
2023-11-06 10:50 ` [PATCH net 0/4] vsock: fix server prevents clients from reconnecting Stefano Garzarella
2023-11-07 22:30 ` patchwork-bot+netdevbpf [this message]
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=169939622521.29953.960000418979346249.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=asias@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.storniolo95@gmail.com \
--cc=imbrenda@linux.vnet.ibm.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luigi.leonardi@outlook.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.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