Re: [PATCH net v2 0/2] vsock: Fix SO_ZEROCOPY on accept()ed vsocks
From: patchwork-bot+netdevbpf@kernel.org
Date: 2026-01-06 00:23:30
Also in:
lkml, virtualization
From: patchwork-bot+netdevbpf@kernel.org
Date: 2026-01-06 00:23:30
Also in:
lkml, virtualization
Hello: This series was applied to netdev/net.git (main) by Jakub Kicinski [off-list ref]: On Mon, 29 Dec 2025 20:43:09 +0100 you wrote:
vsock has its own handling of setsockopt(SO_ZEROCOPY). Which works just fine unless socket comes from a call to accept(). Because SOCK_CUSTOM_SOCKOPT flag is missing, attempting to set the option always results in errno EOPNOTSUPP. Signed-off-by: Michal Luczaj <redacted> [...]
Here is the summary with links:
- [net,v2,1/2] vsock: Make accept()ed sockets use custom setsockopt()
https://git.kernel.org/netdev/net/c/ce5e612dd411
- [net,v2,2/2] vsock/test: Test setting SO_ZEROCOPY on accept()ed socket
https://git.kernel.org/netdev/net/c/caa20e9e155b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html