From: Jakub Kicinski <kuba@kernel.org>
To: Michal Luczaj <mhal@rbox.co>
Cc: Stefano Garzarella <sgarzare@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
George Zhang <georgezhang@vmware.com>,
Dmitry Torokhov <dtor@vmware.com>, Andy King <acking@vmware.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net v2 0/6] vsock: Transport reassignment and error handling issues
Date: Mon, 27 Jan 2025 13:49:39 -0800 [thread overview]
Message-ID: <20250127134939.78613534@kernel.org> (raw)
In-Reply-To: <20250121-vsock-transport-vs-autobind-v2-0-aad6069a4e8c@rbox.co>
On Tue, 21 Jan 2025 15:44:01 +0100 Michal Luczaj wrote:
> Series deals with two issues:
> - socket reference count imbalance due to an unforgiving transport release
> (triggered by transport reassignment);
> - unintentional API feature, a failing connect() making the socket
> impossible to use for any subsequent connect() attempts.
Looks like the merge window merges made this series no longer apply.
Could you rebase & repost?
--
pw-bot: cr
next prev parent reply other threads:[~2025-01-27 21:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 14:44 [PATCH net v2 0/6] vsock: Transport reassignment and error handling issues Michal Luczaj
2025-01-21 14:44 ` [PATCH net v2 1/6] vsock: Keep the binding until socket destruction Michal Luczaj
2025-01-21 14:44 ` [PATCH net v2 2/6] vsock: Allow retrying on connect() failure Michal Luczaj
2025-01-22 16:28 ` Luigi Leonardi
2025-01-22 21:06 ` Michal Luczaj
2025-01-23 11:42 ` Luigi Leonardi
2025-01-21 14:44 ` [PATCH net v2 3/6] vsock/test: Introduce vsock_bind() Michal Luczaj
2025-01-22 16:01 ` Luigi Leonardi
2025-01-22 20:11 ` Michal Luczaj
2025-01-23 11:02 ` Luigi Leonardi
2025-01-23 11:07 ` Stefano Garzarella
2025-01-21 14:44 ` [PATCH net v2 4/6] vsock/test: Introduce vsock_connect_fd() Michal Luczaj
2025-01-22 11:39 ` Stefano Garzarella
2025-01-21 14:44 ` [PATCH net v2 5/6] vsock/test: Add test for UAF due to socket unbinding Michal Luczaj
2025-01-22 11:43 ` Stefano Garzarella
2025-01-21 14:44 ` [PATCH net v2 6/6] vsock/test: Add test for connect() retries Michal Luczaj
2025-01-22 11:43 ` Stefano Garzarella
2025-01-22 15:39 ` Luigi Leonardi
2025-01-22 11:45 ` [PATCH net v2 0/6] vsock: Transport reassignment and error handling issues Stefano Garzarella
2025-01-22 14:16 ` Michal Luczaj
2025-01-22 15:47 ` Stefano Garzarella
2025-01-22 20:10 ` Michal Luczaj
2025-01-27 21:49 ` Jakub Kicinski [this message]
2025-01-28 13:18 ` Michal Luczaj
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=20250127134939.78613534@kernel.org \
--to=kuba@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=mhal@rbox.co \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
/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).