Project

General

Profile

Actions

Bug #4778

closed

flow/bypass: app-layer/stream resources not freed when bypass activated

Added by Victor Julien about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:
Needs backport to 6.0

Description

When a flow bypass is activated, the flow holds on to whatever memory is used in the app-layer and stream. These will finally be freed at the end of the flow. This is not efficient, as after the bypass no code paths will use the app-layer state, transactions or segments.

We might want to hold on to the Tcp session, as this is where TCP packet flags are taken from.


Related issues 2 (0 open2 closed)

Related to Suricata - Bug #4650: Stream TCP raw reassembly is leakingClosedVictor JulienActions
Copied to Suricata - Bug #4971: flow/bypass: app-layer/stream resources not freed when bypass activatedClosedShivani BhardwajActions
Actions

Also available in: Atom PDF