Bug #5113
closed
Off-by-one in flow-manager flow_hash row allocation
Added by Jeff Lucovsky almost 3 years ago.
Updated over 2 years ago.
Description
When configuring more than one flow manager, a single row between the per-flow-manager ranges is left-out.
The current code doesn't cover all rows when more than one flow manager is
used. It leaves a single row between ftd->max and ftd->min of the next
manager orphaned. As an example:
hash_size=1000
flowmgr_number=3
range=333
instance ftd->min ftd->max
0 0 333
1 334 666
2 667 1000
Rows not covered: 333, 666
PR: https://github.com/OISF/suricata/pull/6993
- Copied from Bug #5073: Off-by-one in flow-manager flow_hash row allocation added
- Target version changed from 5.0.9 to 5.0.10
Needs investigation if this is a real issue in 5. Flow engine was largely rewritten in 6+.
- Status changed from Assigned to In Progress
Cherry-pick commit(s):
- 8ef066318d7c4dd9b6686dbebd621c790828c384
- Status changed from In Progress to In Review
- Status changed from In Review to Closed
Also available in: Atom
PDF