Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-8340

Failpoint for recv errors in sock.cpp is injected too late in code path.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: 2.3.2
    • Fix Version/s: 2.4.0-rc1
    • Component/s: Internal Code
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL

      Description

      The socket library failpoint for 'recv' does not share a conditional expression with the evaluation of the return value of 'recv': instead, it is currently placed in the error handling function _handleRecvError. This is too late: if the failpoint is enabled, it will only be triggered if 'recv' actually fails, rather than making it appear as if 'recv' failed. The failpoint must be moved earlier, so that it can influence the apparent success or failure of recv.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              acm Andrew Morrow
              Reporter:
              acm Andrew Morrow
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: