Coverity found a Quality issue: Data race condition

Details:

Coverity Issue ID: 184397
Issue Description: Thread shared data is accessed without holding an appropriate lock, possibly causing a race condition
Potential Impact: The value of the shared data will be determined by the interleaving of thread execution.
Coverity checker: MISSING_LOCK
Branch: v8.2
File path: /src/mongo/util/fail_point.h
Line number: Unknown

What Coverity Detected (Main Finding)

Accessing "this->_data" without holding lock "mongo::FailPoint::Impl._modMutex". Elsewhere, "mongo::FailPoint::Impl._data" is written to with "Impl._modMutex" held 1 out of 1 times.

The issue can be viewed in Coverity here.

How do I fix this?

Refer to https://wiki.corp.mongodb.com/spaces/HGTC/pages/385852267/Guidance+on+fixing+Coverity+issues for guidance on fixing Coverity issues.

This is a false positive, what do I do?

Close the ticket and choose the appropriate resolution. Make sure to include a comment explaining why this is a false positive.

Note: This issue was found on the v8.2 branch. If a fix is needed, you must create a BACKPORT ticket following the Server BACKPORT policy