There is a harmless race between a thread performing an operation using DBDirectClient that temporarily resets the ReadConcernArgs (example) and the currentOps method reading the ReadConcernArgs of the target operation (code).

The main risk potential for this is an operation printing potentially wrong information for the read concern used. This would occur if the currentOp thread acquired a copy of the data while the temporary reset was happening.