From: patchwork-bot+netdevbpf@kernel.org
To: Nguyen Dinh Phi <phind.uet@gmail.com>
Cc: sgarzare@redhat.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
dtor@vmware.com, acking@vmware.com, georgezhang@vmware.com,
virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/3] vsock: fix stale sk_err handling after a failed connect
Date: Tue, 18 Aug 2026 13:00:54 +0000 [thread overview]
Message-ID: <178705805497.2073627.6439611667147974216.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260813173024.2362935-1-phind.uet@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 14 Aug 2026 01:30:17 +0800 you wrote:
> A socket whose connect() failed keeps sk_err set. If that socket is
> later reused as a listener, vsock_accept() rejects an unrelated
> incoming connection, and on virtio/hyperv the resulting child socket
> is leaked.
>
> Patch 1 removes the listener's sk_err check from vsock_accept(), since
> no vsock transport ever sets sk_err on a TCP_LISTEN socket. This will
> fix what the syzbot reported.
>
> [...]
Here is the summary with links:
- [v6,1/3] vsock: don't check the listener's sk_err in vsock_accept()
https://git.kernel.org/netdev/net/c/b8c899cf5e7b
- [v6,2/3] vsock: remove the now-unused rejected flag
https://git.kernel.org/netdev/net/c/81fc0f369637
- [v6,3/3] vsock: use sock_error() to consume sk_err after a failed connect
https://git.kernel.org/netdev/net/c/96cbf8999309
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:[~2026-08-18 13:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 17:30 [PATCH v6 0/3] vsock: fix stale sk_err handling after a failed connect Nguyen Dinh Phi
2026-08-13 17:30 ` [PATCH v6 1/3] vsock: don't check the listener's sk_err in vsock_accept() Nguyen Dinh Phi
2026-08-14 9:03 ` Stefano Garzarella
2026-08-13 17:30 ` [PATCH v6 2/3] vsock: remove the now-unused rejected flag Nguyen Dinh Phi
2026-08-14 9:04 ` Stefano Garzarella
2026-08-13 17:30 ` [PATCH v6 3/3] vsock: use sock_error() to consume sk_err after a failed connect Nguyen Dinh Phi
2026-08-18 13:00 ` 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=178705805497.2073627.6439611667147974216.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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=phind.uet@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.