| commit | 39a96ee16eeec51774f9f52a783cf624a0de4ccb | [log] [tgz] |
|---|---|---|
| author | Christopher Faulet <cfaulet@haproxy.com> | Mon Apr 08 10:52:21 2019 +0200 |
| committer | Christopher Faulet <cfaulet@haproxy.com> | Fri Apr 12 22:06:53 2019 +0200 |
| tree | e5786b74cb892ba6d20e82550b33a472d25398cb | |
| parent | 73c1207c7196f3c1fc814e424e6b486cc5f3afb2 [diff] |
MEDIUM: muxes: Be prepared to don't own connection during the release This happens during mux upgrades. In such case, when the destroy() callback is called, the connection points to a different mux's context than the one passed to the callback. It means the connection is owned by another mux. The old mux is then released but the connection is not closed.