Windows 2012 R2 closesocket() hangs on listening socket

8
votes

I have a weird situation on a production server.

We have network application written on C++ which serves users requests by TCP written using IOCP.

Two days ago we did an update of Windows 2012 R2 (it installed latest security updates. The previous update was 6 month ago). And after the update when trying to stop the service we see in logs that server hangs on call to close listening socket

closesocket(session->listen_socket);

The schema of stopping the network system is the next:

  1. PostQueuedCompletionStatus(m_completion_port, 0, NULL, NULL); x the number of worker threads

  2. Wait all worker threads finish their job

  3. CloseHandle(m_completion_port);

  4. closesocket(session->accept_socket);

    closesocket(session->listen_socket);

This was working good for the last 4 years, but suddenly after Windows 2012 R2 update the server hangs forever on call closesocket(session->listen_socket);

I've alsi tried as a solution to set LINGER option with 0 timeout to make abotive closure, but it didn't help.

All ideas how to fix this or make any additional diagnostics?

1
c++windowssocketsnetworkingiocp
first of all - look stack trace of call closesocket - where exactly code hung. are inside call NtClose or in another place - RbMm
@RbMm ntdll.dll!NtClose() mswsock.dll!SockCloseSocket() mswsock.dll!WSPCloseSocket() ws2_32.dll!closesocket() Unknown - Valentin
this mean hang was in kernel mode driver. even don't know what in this situation do next - RbMm
@RbMm Removing KB4338815 fixed this issue on all our servers. Thanks for help! - Valentin
@MSchenkel See my answer in stackoverflow.com/questions/51372116/… for Microsoft's patch for the issue - CSakura

1 Answers

6
votes

The issue was brought by patch from Microsoft KB4338815, which caused closesocket tо hang forever on Intel Xeon processors and this was also posted by FileZilla guys in this thread https://forum.filezilla-project.org/viewtopic.php?t=49308