Bug #4654: tcp: insert_data_normal_fail can hit without triggering memcap - Suricata - Open Information Security Foundation

Actions

Bug #4654

closed

tcp: insert_data_normal_fail can hit without triggering memcap

Added by Peter Manev about 3 years ago. Updated about 3 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Target version:

Affected Versions:

6.0.3, git master

Effort:

Difficulty:

Label:

Needs backport to 5.0, Needs backport to 6.0

Description

(originally reported y Eric Leblond)

It seems it is failing only on memory issue but we don't see memcap firing. And the memory usage is close the defined memcap.
Patch for this: https://github.com/regit/suricata/commit/bc31dfac420f3186e6c9c8890aa75895ff32ede8

Related issues 3 (0 open — 3 closed)

Actions

#1

Updated by Andreas Herz about 3 years ago

Related to Bug #4502: TCP reassembly memuse approaching memcap value results in TCP detection being stopped added

Actions

#2

Updated by Victor Julien about 3 years ago

Status changed from New to Closed
Assignee set to Eric Leblond
Target version set to 7.0.0-beta1
Label Needs backport to 5.0, Needs backport to 6.0 added

https://github.com/OISF/suricata/commit/0e70958e67398f599b77ba991dc631e025cae5f4
https://github.com/OISF/suricata/commit/c1bffa9545b8aa9d0fc64ac6511edd34919135d7

Actions

#3

Updated by Victor Julien about 3 years ago

Subject changed from insert_data_normal_fail can hit without triggering memcap in counters to tcp: insert_data_normal_fail can hit without triggering memcap

Actions

#4

Updated by Jeff Lucovsky about 3 years ago

Copied to Bug #4818: tcp: insert_data_normal_fail can hit without triggering memcap added

Actions

#5

Updated by Jeff Lucovsky about 3 years ago

Copied to Bug #4819: tcp: insert_data_normal_fail can hit without triggering memcap added

Actions

Also available in: Atom PDF