You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we have _any_ block operations in the deferred queue (i.e. because
we're encrypting a large write in the thread pool), then every block
operation must go through the queue to preserve ordering.
Unfortunately, we were checking the **wrong** `DeferredQueue` when
checking whether to defer writes. This means that a large (deferred)
write followed by a short (non-deferred) write could be reordered so
that the short write happens first.
This is probably the root cause of CI failures that we saw in #1445:
fast-ack means that the Guest is able to send the short write with less
delay, making it more likely to hit this race condition.
0 commit comments