98afc4ec7d
A qcs instance free may be postponed in stream detach operation if the stream is not locally closed. This condition is there to achieve transfering data still present in Tx buffer. Once all data have been emitted to quic-conn layer, qcs instance can be released. However, the stream is only closed locally if HTX EOM has been seen or it has been resetted. In case the transfer finished without EOM, a detached qcs won't be freed even if there is no more activity on it. This bug was not reproduced but was found on code analysis. Its precise impact is unknown but it should not cause any leak as all qcs instances are freed with its parent qcc connection : this should eventually happen on MUX timeout or QUIC idle timeout. To adjust this, condition to mark a stream as locally closed has been extended. On qcc_streams_sent_done() notification, if its Tx buffer has been fully transmitted, it will be closed if either FIN STREAM was set or the stream is detached. This must be backported up to 2.6. (cherry picked from commit 3dc4e5a5b947aa55b65a6bde17bbce331586894b) Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)