[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20251223-vsock-child-sock-custom-sockopt-v1-0-4654a75d0f58@rbox.co>
Date: Tue, 23 Dec 2025 10:15:27 +0100
From: Michal Luczaj <mhal@...x.co>
To: Stefano Garzarella <sgarzare@...hat.com>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>,
Arseniy Krasnov <avkrasnov@...utedevices.com>
Cc: virtualization@...ts.linux.dev, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, Michal Luczaj <mhal@...x.co>
Subject: [PATCH net 0/2] vsock: Fix SO_ZEROCOPY on accept()ed vsocks
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 <mhal@...x.co>
---
Michal Luczaj (2):
vsock: Make accept()ed sockets use custom setsockopt()
vsock/test: Test setting SO_ZEROCOPY on accept()ed socket
net/vmw_vsock/af_vsock.c | 1 +
tools/testing/vsock/vsock_test.c | 33 +++++++++++++++++++++++++++++++++
2 files changed, 34 insertions(+)
---
base-commit: 5e7365b5a1ac8f517a7a84442289d7de242deb76
change-id: 20251222-vsock-child-sock-custom-sockopt-23b779c30c8f
Best regards,
--
Michal Luczaj <mhal@...x.co>
Powered by blists - more mailing lists