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]> --- Changes in v2: - Fix: set socket flags in a consistent way [Stefano] - Test: simplify sync by removing sync [Stefano] - Link to v1: https://lore.kernel.org/r/20251223-vsock-child-sock-custom-sockopt-v1-0-4654a75d0...@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 | 4 ++++ tools/testing/vsock/vsock_test.c | 32 ++++++++++++++++++++++++++++++++ 2 files changed, 36 insertions(+) --- base-commit: 58fc7342b529803d3c221101102fe913df7adb83 change-id: 20251222-vsock-child-sock-custom-sockopt-23b779c30c8f Best regards, -- Michal Luczaj <[email protected]>
