evoskuil opened this issue 8 years ago · 1 comments
This should not be the case unless the spin lock is outside of the flush lock.
This has been resolved for 3.2/4.0 though the elimination of the spin lock. Reads are no longer disrupted by intervening writes in any case.