When the currentOpSpawnsThreadWaitingForLatch failpoint is enabled, the interruptibleState thread attempts to acquire _m while holding interruptibleState.mutex. This represents an inversion of the normal _m -> interruptibleState.mutex locking order.

Possible solutions to investigate:

• Temporarily release the interruptibleState.mutex lock when calling setIsWaiting
• Obviate the _m lock by using atomics in setIsWaiting