Project

General

Profile

Actions

Bug #3861

closed

flow: check flow bypass handling

Added by Victor Julien almost 4 years ago. Updated over 3 years ago.

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

Description

After flow engine changes flow bypass might not work correctly: test this.

2 main areas of interest:
- src/flow-hash.c::FlowGetFromFlowKey no longer does a flow queue fetch. It needs to be updated to have a local storage for flow pool blocks
- flow manager hash walk does something for these flows, but its unclear if that is still correct


Related issues 1 (0 open1 closed)

Related to Suricata - Bug #3902: flow/bypass: SEGV src/flow.c:1158:9 in FlowUpdateStateClosedEric LeblondActions
Actions #1

Updated by Victor Julien over 3 years ago

  • Related to Bug #3902: flow/bypass: SEGV src/flow.c:1158:9 in FlowUpdateState added
Actions #2

Updated by Eric Leblond over 3 years ago

I did get a look at second point and it seems to be correct. Checking the first one.

Actions #3

Updated by Victor Julien over 3 years ago

  • Status changed from Assigned to Closed
  • Priority changed from High to Normal

Looks like we're good.

Actions

Also available in: Atom PDF