[v1] vsock: Fix SO_ZEROCOPY on accept()ed vsocks

[PATCH net 0/2] vsock: Fix SO_ZEROCOPY on accept()ed vsocks

Michal Luczaj posted 2 patches 1 month, 2 weeks ago

Diff against v2
Download series mbox

There is a newer version of this series

net/vmw_vsock/af_vsock.c         |  1 +
tools/testing/vsock/vsock_test.c | 33 +++++++++++++++++++++++++++++++++
2 files changed, 34 insertions(+)

Expand all Fold all

[PATCH net 0/2] vsock: Fix SO_ZEROCOPY on accept()ed vsocks

Posted by Michal Luczaj 1 month, 2 weeks ago

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@rbox.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@rbox.co>