From: Willy Tarreau Date: Tue, 17 Nov 2026 16:41:01 +0000 (+0100) Subject: BUG/MAJOR: h3: do not panic on HTX_FL_PARSING_ERROR after htx_xfer() X-Git-Tag: v3.5-dev13~23 X-Git-Url: https://git.kaiwu.me/http/%7B@url%7D?a=commitdiff_plain;h=9c52a0b088e3958e1f801854b78a04a3819365c1;p=haproxy.git BUG/MAJOR: h3: do not panic on HTX_FL_PARSING_ERROR after htx_xfer() After various tests and a long code analysis, it turns out that this condition which was thought never to be triggerable can finally be triggered if some data cannot be transferred to the channel due to the reserve. The condition is rare but not impossible, so let's get rid of it. This patch must be backported to all stable releases. --- diff --git a/src/qcm_http.c b/src/qcm_http.c index 8eea0dad3..00dd9bebe 100644 --- a/src/qcm_http.c +++ b/src/qcm_http.c @@ -44,7 +44,6 @@ size_t qcs_http_rcv_buf(struct qcs *qcs, struct buffer *buf, size_t count, } htx_xfer(cs_htx, qcs_htx, count, HTX_XFER_DEFAULT); - BUG_ON(qcs_htx->flags & HTX_FL_PARSING_ERROR); /* EOM was copied to cs_htx if all data were copied. */ if (htx_msg_ended(cs_htx)) {