Operations that use the LockerImpl interface for acquiring locks are expected to call the lock/unlock methods from a single thread.

A part of locking a lock involves incrementing the lock stats (_stats in lock_state.h). Single-threaded access to this data structure is not enforced as CurOp can access it concurrently for user reporting purposes.

To fix TSAN build failures in this area we should investigate using AtomicLockStats over SingleThreadedLockStats.