BUG/MEDIUM: stconn: Set fsb date if zero-copy forwarding is blocked during nego
authorChristopher Faulet <cfaulet@haproxy.com>
Fri, 5 Jan 2024 15:59:06 +0000 (16:59 +0100)
committerWilly Tarreau <w@1wt.eu>
Fri, 5 Jan 2024 18:14:52 +0000 (19:14 +0100)
commitc38c1d02c5b67823d3d157eb2e5ce6df42994aba
tree597626ad6e5e87faa5663e8fc4140b9ff1cca53f
parent2b52339ac0fefd9561372e7a777f098dfa00ef1d
BUG/MEDIUM: stconn: Set fsb date if zero-copy forwarding is blocked during nego

During the zero-copy forwarding, if the consumer side reports it is blocked,
it means it is blocked on send. At the stream-connector level, the event
must be reported to be sure to set/update the fsb date. Otherwise, write
timeouts cannot be properly reported. If this happens when no other timeout
is armed, this freezes the stream.

This patch must be backported to 2.9.

(cherry picked from commit 7cc41514226a2072b538c859cd83dc01de0aeb3f)
Signed-off-by: Willy Tarreau <w@1wt.eu>
include/haproxy/stconn.h