Set SO_UPDATE_ACCEPT_CONTEXT on sockets accepted via AcceptEx in PortRelay

[wangxin12]

Summary of the Pull Request

After AcceptEx completes, set SO_UPDATE_ACCEPT_CONTEXT to mark the socket as connected. Without this, getpeername/getsockname/shutdown and a number of setsockopt/getsockopt options fail on the accepted socket.

PR Checklist

• Closes: Link to issue #xxx
• Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
• Tests: Added/updated if needed and all pass
• Localization: All end user facing strings can be localized
• Dev docs: Added/updated if needed
• Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

[Copilot]

Pull request overview

This PR updates the Windows port relay implementations to call setsockopt(..., SO_UPDATE_ACCEPT_CONTEXT, ...) on sockets accepted via AcceptEx, ensuring the accepted socket is fully “connected” from Winsock’s perspective (enabling getpeername/getsockname/shutdown and related socket options to work correctly).

Changes:

• Set SO_UPDATE_ACCEPT_CONTEXT after AcceptEx completion in the wslrelay localhost port relay (both async-completion and synchronous-completion paths).
• Set SO_UPDATE_ACCEPT_CONTEXT after AcceptEx completion in the wslcsession PortRelayAcceptHandle accept path.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
src/windows/wslrelay/localhost.cpp	Updates the PortRelay accept flow to set SO_UPDATE_ACCEPT_CONTEXT on the accepted socket before relaying.
src/windows/wslcsession/PortRelayHandle.cpp	Updates PortRelayAcceptHandle::Collect() to set SO_UPDATE_ACCEPT_CONTEXT prior to launching the relay thread.

[benhillis]

Can you add a regression test please?

[wangxin12]

Can you add a regression test please?

Hi @benhillis , I looked into this and ran into a few obstacles that make a meaningful regression test hard. Wanted to walk through them and get your input on the best path forward.

1. The accepted socket is not exposed, so we can't directly call APIs like shutdown on it to test.
2. The current wsl::windows::common::relay::BidirectionalRelay logs and swallows the failure, and relay loop tears down both directions on the first EOF either way. From the client's perspective the connection still closes cleanly — just via closesocket instead of orderly shutdown.

LOG_LAST_ERROR_IF(shutdown(reinterpret_cast<SOCKET>(LeftHandle), SD_SEND) == SOCKET_ERROR)