83ae0c250c
When a RESET_STREAM is received, QCS Rx channel is closed and pending Rx data and buf are cleared without being transmitted to upper stream layer. This can cause an issue if this QCS instance is present in the QCC recv_list. When qcc_io_recv() is executed after reset handling, an infinite loop is triggered for the QCS instance as qcs_rx_avail_data() always return 0. This issue happened due to the poor writing of the while loop in qcc_io_recv() which is not correctly protected against infinite execution. To prevent this issue, this patch rewrites the loop. Crucially, LIST_DEL_INIT() is now performed unconditionally outside of the inner loop. This guarantees that even if the inner loop is not executed, the stream will be removed from QCC recv_list and iteration will progress. This is functionally correct as a QCS should not be present in recv_list if there is no avail data or demux is currently blocked. For the first condition, qcc_decode_qcs() will be called again when new data is read unless demux is blocked. In this case, QCS will be reinserted in the list on unblocking, with a rescheduling to invoke qcc_decode_qcs(). In the context of the currently found reproducer linked to stream reset, the QCS instance can be safely removed from the recv_list without implication. This must be backported up to 3.2. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .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.