Serialize concurrent accesses to `Socket` in `ThrowOnNetworkErrorInEnsureSync`

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • v5.2, v5.0
    • Service Arch 2022-1-24
    • 69
    • 1
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Amirsaman Memaripour
            Reporter:
            Amirsaman Memaripour
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: