Hide Forgot
Marking this bug as invalid, since there will be no more than one operation from a single thread in the waiting list of operations waiting for open. As for as the order of operations between two different goes, quick read need not worry about their order, since the threads themselves have to synchronize the order.
The operations waiting for completion of open are stack_wound in a loop in qr_open_cbk. With afr below quick-read, there can be race-conditions among the operations since in afr, an fop is implemented as a transaction. The fix should resume the operations in waiting list one by one making sure that the reply to the first operation in list is got before resuming the next operation.