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 <[email protected]> --- 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 <[email protected]>
