mbox series

[net,0/5] vsock: Transport reassignment and error handling issues

Message ID 20250117-vsock-transport-vs-autobind-v1-0-c802c803762d@rbox.co (mailing list archive)
Headers show
Series vsock: Transport reassignment and error handling issues | expand

Message

Michal Luczaj Jan. 17, 2025, 9:59 p.m. UTC 
Series deals with two issues:
- socket reference count imbalance due to an unforgiving transport release
  (triggered by transport reassignment);
- unintentional API feature, a failing connect() making the socket
  impossible to use for any subsequent connect() attempts.

Signed-off-by: Michal Luczaj <mhal@rbox.co>
---
Michal Luczaj (5):
      vsock: Keep the binding until socket destruction
      vsock: Allow retrying on connect() failure
      vsock/test: Introduce vsock_bind()
      vsock/test: Add test for UAF due to socket unbinding
      vsock/test: Add test for connect() retries

 net/vmw_vsock/af_vsock.c         |  13 +++-
 tools/testing/vsock/util.c       |  56 +++++++---------
 tools/testing/vsock/util.h       |   1 +
 tools/testing/vsock/vsock_test.c | 136 ++++++++++++++++++++++++++++++++++-----
 4 files changed, 155 insertions(+), 51 deletions(-)
---
base-commit: 5d6a361dc01d823cb7c10697f16695d45a82b909
change-id: 20250116-vsock-transport-vs-autobind-2da49f1d5a0a

Best regards,