From: patchwork-bot+netdevbpf@kernel.org
To: Seth Forshee <sforshee@digitalocean.com>
Cc: sgarzare@redhat.com, davem@davemloft.net, kuba@kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] vsock: remove vsock from connected table when connect is interrupted by a signal
Date: Thu, 17 Feb 2022 17:20:10 +0000 [thread overview]
Message-ID: <164511841010.26117.4554387084228726127.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220217141312.2297547-1-sforshee@digitalocean.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 17 Feb 2022 08:13:12 -0600 you wrote:
> vsock_connect() expects that the socket could already be in the
> TCP_ESTABLISHED state when the connecting task wakes up with a signal
> pending. If this happens the socket will be in the connected table, and
> it is not removed when the socket state is reset. In this situation it's
> common for the process to retry connect(), and if the connection is
> successful the socket will be added to the connected table a second
> time, corrupting the list.
>
> [...]
Here is the summary with links:
- [v2] vsock: remove vsock from connected table when connect is interrupted by a signal
https://git.kernel.org/netdev/net/c/b9208492fcae
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:[~2022-02-17 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 14:13 [PATCH v2] vsock: remove vsock from connected table when connect is interrupted by a signal Seth Forshee
2022-02-17 14:30 ` Stefano Garzarella
2022-02-17 17:20 ` 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=164511841010.26117.4554387084228726127.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sforshee@digitalocean.com \
--cc=sgarzare@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).