4f32d03360
In sc_notify(), it remained a case where it was possible to set an expiration date on the stream in the past, leading to a crash because of a BUG_ON(). This must never happen of course. In sc_notify(), The stream's expiration may be updated in case no wakeup conditions are encoutered. In that case, we must take care to never set an expiration date in the past. However, it appeared there was still a condition to do so. This code is based on an implicit postulate: the stream's expiration date must always be set when we leave process_stream(). It was true since the 2.9. But in 3.0, the buffer allocation mechanism was improved and on an alloc failure in process_stream(), the stream is inserted in a wait-list and its expiration date is set to TICK_ETERNITY. With the good timing, and an analysis expiration date set on a channel, it is possible to set the stream's expiration date in past. After analysis, it appeared that the proper way to fix the issue is to only evaluate I/O timers (read and write timeout) and not stream's timers (analase_exp or conn_exp) because only I/O timers may have changed since the last process_stream() call. This patch must be backported as far as 3.0 to fix the issue. But it is probably a good idea to also backported it as far as 2.8. |
||
|---|---|---|
| .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.