mirror of https://github.com/OISF/suricata
pool: don't call Cleanup after failed Init
Stream reassembly memcap is regulated by the Init and Cleanup callbacks. If Init fails due to memcap reached, Cleanup had no way of knowing and it would decrease the memcap even if it hadn't been increased by Init. This could lead to too much memory use and memcap counter underflow. This patch fixes the issue by not calling Cleanup in this case. It's fair to see a failed Init the responsibility of Init.pull/3898/head
parent
597ff3c8e3
commit
9ea6db3889
Loading…
Reference in New Issue