[PATCH net v4] vsock: fix connect() races

[Michal Luczaj]

Handle a racy socket change in connect(). This iteration focuses on a
single issue and aims for minimal changes.

I'm keeping this as a 1-patch series so as not to confuse the patchwork.

---
Changes in v4:
- Defer all other patches to net-next (Stefano)
- Link to v3: https://patch.msgid.link/20260922-vsock-connect-reset-closing-v3-0-78907b8200d4@xxxxxxx

Changes in v3:
- Change the transport assignment life cycle (Stafano)
- Expand comments (Stafano)
- CC: drop bouncing address
- Link to v2: https://patch.msgid.link/20260915-vsock-connect-reset-closing-v2-0-a1d9abb472f7@xxxxxxx

Changes in v2:
- CC: drop bouncing addresses
- Add more related fixes
- Handle ENOBUFS (Bobby)
- Consume sk_err (Stefano)
- Link to v1: https://patch.msgid.link/20260909-vsock-connect-reset-closing-v1-1-50298b9ccfbf@xxxxxxx

---
Michal Luczaj (1):
      vsock: treat TCP_CLOSING as once-established

 net/vmw_vsock/af_vsock.c | 17 ++++++++---------
 1 file changed, 8 insertions(+), 9 deletions(-)
---
base-commit: 6dc989ea46b96ce170840174b4a38c4a387fb005
change-id: 20260820-vsock-connect-reset-closing-98dd28769d7f

Best regards,
--  
Michal Luczaj <mhal@xxxxxxx>