Thread (7 messages) flat view 7 messages, 3 authors, 29d ago

Re: [PATCH v6 0/3] vsock: fix stale sk_err handling after a failed connect

From: patchwork-bot+netdevbpf@kernel.org
Date: 2026-08-18 13:01:43
Also in: lkml, virtualization

Hello:

This series was applied to netdev/net.git (main)
by Paolo Abeni [off-list ref]:

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

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help