Project

General

Profile

Actions
Copy link

Bug #4971

closed

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

Added by Shivani Bhardwaj almost 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Shivani Bhardwaj
Target version:
6.0.5
Affected Versions:
Effort:
Difficulty:
Label:

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 1 (0 open — 1 closed)

Copied from Suricata - Bug #4778: flow/bypass: app-layer/stream resources not freed when bypass activatedClosedVictor JulienActions
Actions
Copy link
 #1

Updated by Shivani Bhardwaj almost 3 years ago

  • Copied from Bug #4778: flow/bypass: app-layer/stream resources not freed when bypass activated added
Actions
Copy link
 #2

Updated by Shivani Bhardwaj almost 3 years ago

Commit 536291054c9694070beac1d19b41bf8a1f9c1d4e +b19d1df69f47b4b85337f1695bc770f4b0703bac

Actions
Copy link
 #3

Updated by Shivani Bhardwaj almost 3 years ago

  • Target version changed from 7.0.0-beta1 to 6.0.5
  • Label deleted (Needs backport to 6.0)
Actions
Copy link
 #4

Updated by Shivani Bhardwaj almost 3 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #5

Updated by Shivani Bhardwaj almost 3 years ago

  • Status changed from In Progress to In Review
Actions
Copy link
 #6

Updated by Shivani Bhardwaj almost 3 years ago

  • Status changed from In Review to Closed
Actions
Copy link

Also available in: Atom PDF