mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-24 07:11:20 +02:00
19ef6369b5
When entering quic_sock_fd_iocb() I/O handler which is responsible of recvfrom() datagrams, the first thing which is done it to try to reuse a dgram object containing metadata about the received datagrams which has been consumed by the connection thread. If this object could not be used for any reason, so when we "goto out" of this function, we must release the memory allocated for this objet, if not it will leak. Most of the time, this happened when we fulfilled a buffer as reported in GH #1749 by Tristan. This is why we added a pool_free() call just before the out label. We mark <new_dgram> as NULL when it successfully could be used. Thank you for Tristan and Willy for their participation on this issue. Must be backported to 2.6.
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)