Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
BUG/MINOR: mux-quic: do not prevent non-STREAM sending on flow control
Data emitted by QUIC MUX is restrained by the peer flow control. This is checked on stream and connection level inside qcc_io_send(). The connection level check was placed early in qcc_io_send() preambule. However, this also prevents emission of other frames STOP_SENDING and RESET_STREAM, until flow control limitation is increased by a received MAX_DATA. Note that local flow control frame emission is done prior in qcc_io_send() and so are not impacted. In the worst case, if no MAX_DATA is received for some time, this could delay significantly streams closure and resource free. However, this should be rare as other peers should anticipate emission of MAX_DATA before reaching flow control limit. In the end, this is also covered by the MUX timeout so the impact should be minimal To fix this, move the connection level check directly inside QCS sending loop. Note that this could cause unnecessary looping when connection flow control level is reached and no STOP_SENDING/RESET_STREAM are needed. This should be backported up to 2.6. (cherry picked from commit 333f2ca) Signed-off-by: Christopher Faulet <[email protected]> (cherry picked from commit 696337f) Signed-off-by: Christopher Faulet <[email protected]> (cherry picked from commit 61e9109) Signed-off-by: Christopher Faulet <[email protected]> (cherry picked from commit 445e15a) [ad: fix context] Signed-off-by: Amaury Denoyelle <[email protected]>
- Loading branch information