c7004be964
When a QCS instance is fully closed on qcs_close_remote() invokation, it is moved into purg_list for later cleanup. This reuses <el_send> list element, so a BUG_ON() ensures that QCS is not already present in send_list. This code is safe for bidirectional streams, as local channel is only closed after FIN or RESET_STREAM emission completion, so such QCS won't be present in the send_list on full closure. However, things are different for remote uni streams. As such streams do not have any local channel, qcs_close_remote() will always proceed to full closure. Most of the time this is fine, but the aformentionned BUG_ON() could be triggered if emission is required on a remote uni stream : this only happens after read was aborted and a STOP_SENDING frame is prepared. Fix this by adding an extra operation in qcs_close_remote() : on full close, STOP_SENDING is cancelled if it was prepared and the QCS instance is removed from send_list. This is safe as STOP_SENDING is unnecessary after the remote channel is closed. This operation is performed before purg_list insertion which prevents the BUG_ON() crash issue. This patch must be backported up to 3.1. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| BSDmakefile | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README.md | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
HAProxy
HAProxy is a free, very fast and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
Installation
The INSTALL file describes how to build HAProxy. A list of packages is also available on the wiki.
Getting help
The discourse and the mailing-list are available for questions or configuration assistance. You can also use the slack or IRC channel. Please don't use the issue tracker for these.
The issue tracker is only for bug reports or feature requests.
Documentation
The HAProxy documentation has been split into a number of different files for ease of use. It is available in text format as well as HTML. The wiki is also meant to replace the old architecture guide.
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)
License
HAProxy is licensed under GPL 2 or any later version, the headers under LGPL 2.1. See the LICENSE file for a more detailed explanation.