]> git.ipfire.org Git - thirdparty/suricata.git/commit
flow-manager: move time check after RUNNNING state change
authorLukas Sismis <lsismis@oisf.net>
Sun, 27 Apr 2025 10:56:02 +0000 (12:56 +0200)
committerVictor Julien <victor@inliniac.net>
Wed, 21 May 2025 07:37:24 +0000 (09:37 +0200)
commit58df9703913201c8eecaea5c3b9bd6fb79eb7128
tree3e48e1d3dc30f9a70d1d989c7add3fa0da8b129c
parentb8e4ba6e3ee936e72cc605a931852a54e131ae1c
flow-manager: move time check after RUNNNING state change

When running in pcap-file mode and with a continous directory
reading, the provided directory can be empty.
By having no packets and being in offline mode, the initial packet timestamp
is never set. However, Flow Manager waited until the timestamp was set
to proceed with transferring its state to "RUNNING".
Other pcap-related threads (RX / workers) are set in RUNNING state while
waiting for the PCAP to appear in the directory.

As a result, the main Suricata-Main thread timed out after the default
60 seconds budget for threads to turn from INIT_DONE to RUNNING state.

Ticket: 7568
src/flow-manager.c