Serialize concurrent accesses to `Socket` in `TCPResetAfterConnectionIsSilentlySwallowed`

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • v5.2, v5.0
    • Service Arch 2021-12-13, Service Arch 2022-1-10, Service Arch 2022-1-24
    • 25
    • 3
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Reo Kimura (Inactive)
              Reporter:
              Amirsaman Memaripour
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: