| commit | 7c452ccbff8261ead35c1bd8c932a8d4e4a3e451 | [log] [tgz] |
|---|---|---|
| author | Christopher Faulet <cfaulet@haproxy.com> | Thu Apr 14 11:08:26 2022 +0200 |
| committer | Christopher Faulet <cfaulet@haproxy.com> | Thu Apr 14 11:57:05 2022 +0200 |
| tree | 9a65789220b0e908c1509d098a4a382c3ad299f9 | |
| parent | 86b08a3e3eb62d6642604846db3e40db37b91b16 [diff] |
MINOR: muxes: Don't expect to have a mux without connection in destroy callback Once a mux initialized, the underlying connection alwaus exists from its point of view and it is never removed until the mux is released. It may be owned by another mux during an upgrade. But the pointer remains set. Thus there is no reason to test it in the destroy callback function. This patch should fix the issue #1652.