From: patchwork-bot+netdevbpf@kernel.org
To: Michal Luczaj <mhal@rbox.co>
Cc: sgarzare@redhat.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
georgezhang@vmware.com, acking@vmware.com, dtor@vmware.com,
virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] vsock: Ignore signal/timeout on connect() if already established
Date: Thu, 20 Nov 2025 16:10:09 +0000 [thread overview]
Message-ID: <176365500951.1690915.18295352732751335055.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251119-vsock-interrupted-connect-v2-1-70734cf1233f@rbox.co>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 19 Nov 2025 15:02:59 +0100 you wrote:
> During connect(), acting on a signal/timeout by disconnecting an already
> established socket leads to several issues:
>
> 1. connect() invoking vsock_transport_cancel_pkt() ->
> virtio_transport_purge_skbs() may race with sendmsg() invoking
> virtio_transport_get_credit(). This results in a permanently elevated
> `vvs->bytes_unsent`. Which, in turn, confuses the SOCK_LINGER handling.
>
> [...]
Here is the summary with links:
- [net,v2] vsock: Ignore signal/timeout on connect() if already established
https://git.kernel.org/netdev/net/c/002541ef650b
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:[~2025-11-20 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 14:02 [PATCH net v2] vsock: Ignore signal/timeout on connect() if already established Michal Luczaj
2025-11-19 16:54 ` Stefano Garzarella
2025-11-20 16:10 ` 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=176365500951.1690915.18295352732751335055.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acking@vmware.com \
--cc=davem@davemloft.net \
--cc=dtor@vmware.com \
--cc=edumazet@google.com \
--cc=georgezhang@vmware.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhal@rbox.co \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=virtualization@lists.linux.dev \
/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