-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Internal Code
-
Fully Compatible
-
ALL
-
v5.2, v5.0
-
Service Arch 2022-1-24
-
69
-
1
The main thread attempts to close the socket (here), while the connection thread is running setsockopt on the socket (here). We need to serialize accesses to the socket object to fix the data-race.
This is almost identical to the issue reported in SERVER-61107 and the same fix may apply here.
- is duplicated by
-
SERVER-87947 Data race on ConnectionThread::_s in ThrowOnNetworkErrorInEnsureSync unittest
- Closed
- is related to
-
SERVER-61107 Serialize concurrent accesses to `Socket` in `TCPResetAfterConnectionIsSilentlySwallowed`
- Closed