BUG/MINOR: sink: Use the right field in appctx context in release callback

In the release callback, ctx.peers was used instead of ctx.sft. Concretly,
it is not an issue because the appctx context is an union and these both
fields are structures with a unique pointer. But it will be a problem if
that changes.

This patch must be backported as far as 2.2.

(cherry picked from commit dd0b144c3ae83c2ea14f969cb58fa4b927c2c455)
Signed-off-by: William Lallemand <wlallemand@haproxy.org>
(cherry picked from commit eed3cab77026bafde5277788580e9b42bdd81df5)
Signed-off-by: Willy Tarreau <w@1wt.eu>
(cherry picked from commit efebfdad954f99ee198b4020d7e626a0c2d4c447)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>

diff --git a/src/sink.c b/src/sink.c
index 9e5e639..88c498b 100644 (file)
--- a/src/sink.c
+++ b/src/sink.c
@@ -602,7 +602,7 @@ void __sink_forward_session_deinit(struct sink_forward_target *sft)
 
 static void sink_forward_session_release(struct appctx *appctx)
 {
-       struct sink_forward_target *sft = appctx->ctx.peers.ptr;
+       struct sink_forward_target *sft = appctx->ctx.sft.ptr;
 
        if (!sft)
                return;