mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-09-23 23:01:24 +02:00
49f6f4b1a7
If multiple "bind" lines were present on the "peers" section, multiple listeners were added to a list but the code mistakenly initialize the first member and this first listener was re-configured instead of the newly created one. The last one remains uninitialized causing a null dereference a soon a connection is received. In addition, the 'peers' sections and protocol are not currently designed to handle multiple listeners. This patch check if there is already a listener configured on the 'peers' section when we want to create a new one. This is rising an error if a listener is already present showing the file and line in the error message. To keep the file and line number of the previous listener available for the error message, the 'bind_conf_uniq_alloc' function was modified to keep the file/line data the struct 'bind_conf' was firstly allocated (previously it was updated each time the 'bind_conf' was reused). This patch should be backported until version 2.0
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)