mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-01-30 06:22:00 +01:00
cf181c76e3
When a SPOE applet is used to send a frame, a reference on this applet is saved in the spoe context of the offladed stream. But, if the applet is released before receving the corresponding ack, we must be sure to remove this reference. This was performed for fragmented frames only. But it must also be performed for a spoe contexts in the applet waiting_queue and in the thread waiting_queue (used in async mode). This bug leads to a memory corruption when an offloaded stream try to update the state of a released applet because it still have a reference on it. There are many ways to trigger this bug. The easiest is probably during reloads. On the old process, all applets are woken up to be released ASAP. Many thanks to Maciej Zdeb to report the bug and to work on it for 2 months. Without his help, it would have been much more difficult to fix the bug. It is always a huge pleasure to see how some users are enthousiast and helpful. Thanks again Maciej ! This patch must be backported to all versions where the spoe is supported (>= 1.7).
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)