tree 9945f7eb048cdfc747d4c492a6e3a9d994acffe5
parent 9b98c9d0a2401e4263427a9b505470ed746d6f3a
author Christopher Faulet <cfaulet@haproxy.com> 1710225116 +0100
committer Christopher Faulet <cfaulet@haproxy.com> 1712157523 +0200

BUG/MINOR: listener: Wake proxy's mngmt task up if necessary on session release

When a session is released, listener_release() function is called to notify
the listener. It is an opportunity to resume limited/full listeners. We
first try to resume the listener owning the released session, then all
limited listeners in the global queue and finally all limited listeners in
the frontend's waiting queue. This last step is only performed if there is
no limit applied on the frontend. Nothing is performed if the session rate is
still limited. And it is an issue because if this happens for the last
listener's session, there is no other event to wake the frontend's managment
task up and the listener remains in the limited state.

To fix the issue, when a limit is still applied on the frontent, we must
compute the new wake up date from the sessions rate and schedule the
frontend's managment task.

It is easy to reproduce the issue in SSL by setting a maxconn and a rate
limit on sessions.

This patch should fix the issue #2476. It must be backported to all stable
versions.

(cherry picked from commit 65ae1347c7d0495c70221dca3fdda20a04d53628)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit fb9b868baee8fdecee714c4641e52f2deec2f59b)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit 42b71d9ca931177e89c29bae59e0d3efdd125257)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit 650b3b290f32c789986125d902282f1df9590d8a)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit 55aa51f2b289203888bd1a3c64027bbd8ee0ca8c)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>