Project

General

Profile

Actions
Copy link

Bug #3399

closed

smb: post-GAP some transactions never close

Added by Victor Julien about 5 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Victor Julien
Target version:
5.0.1
Affected Versions:
5.0.0
Effort:
Difficulty:
Label:
Needs backport

Description

In long running flows with lots of transactions and at least one GAP, transactions started prior to the GAP could be left open. This could lead to the tx list getting longer and longer. This in turn would lead to high CPU use and higher than expected memory use.

Related issues 4 (1 open — 3 closed)

Related to Suricata - Bug #3375: Tracking: file tracking/inspection performance issuesNewVictor JulienActions
Related to Suricata - Bug #3400: smb: post-GAP file tx handlingClosedVictor JulienActions
Related to Suricata - Bug #3424: nfs: post-GAP some transactions never closeClosedVictor JulienActions
Copied to Suricata - Bug #3402: smb: post-GAP some transactions never close (4.1.x)ClosedVictor JulienActions
Actions
Copy link
 #2

Updated by Victor Julien about 5 years ago

  • Related to Bug #3375: Tracking: file tracking/inspection performance issues added
Actions
Copy link
 #3

Updated by Victor Julien about 5 years ago

  • Related to Bug #3400: smb: post-GAP file tx handling added
Actions
Copy link
 #4

Updated by Victor Julien about 5 years ago

  • Copied to Bug #3402: smb: post-GAP some transactions never close (4.1.x) added
Actions
Copy link
 #5

Updated by Victor Julien about 5 years ago

  • Related to Bug #3424: nfs: post-GAP some transactions never close added
Actions
Copy link

Also available in: Atom PDF