[SERVER-61107] Serialize concurrent accesses to `Socket` in `TCPResetAfterConnectionIsSilentlySwallowed` Created: 29/Oct/21 Updated: 29/Oct/23 Resolved: 13/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0, 5.0.7, 5.2.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Amirsaman Memaripour | Assignee: | Reo Kimura (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | save-for-reo, servicearch-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v5.2, v5.0
|
||||||||||||||||
| Sprint: | Service Arch 2021-12-13, Service Arch 2022-1-10, Service Arch 2022-1-24 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 25 | ||||||||||||||||
| Story Points: | 3 | ||||||||||||||||
| Description |
|
The test spawns a thread to establish a new connection, and concurrently attempts to close the connection. This causes non-serialized concurrent accesses to the file handle associated with the socket, in particular a read after write data race. Serializing accesses to the socket object (defined here) should prevent the data race. |
| Comments |
| Comment by Githook User [ 21/Mar/22 ] |
|
Author: {'name': 'Reo Kimura', 'email': 'reo.kimura@mongodb.com', 'username': 'rkimura21'}Message: (cherry picked from commit c2eee2a284cf064b25b396f36331af19568a6425) |
| Comment by Githook User [ 23/Feb/22 ] |
|
Author: {'name': 'Reo Kimura', 'email': 'reo.kimura@mongodb.com', 'username': 'rkimura21'}Message: (cherry picked from commit c2eee2a284cf064b25b396f36331af19568a6425) |
| Comment by Githook User [ 13/Jan/22 ] |
|
Author: {'name': 'Reo Kimura', 'email': 'reo.kimura@mongodb.com', 'username': 'rkimura21'}Message: |