Skip to content

capture-bypass: fix worker timeout of bypassed flows v1#15331

Open
adaki4 wants to merge 1 commit intoOISF:mainfrom
adaki4:capture-bypass-worker-flow-timeout-v1
Open

capture-bypass: fix worker timeout of bypassed flows v1#15331
adaki4 wants to merge 1 commit intoOISF:mainfrom
adaki4:capture-bypass-worker-flow-timeout-v1

Conversation

@adaki4
Copy link
Copy Markdown
Contributor

@adaki4 adaki4 commented May 7, 2026

This PR resolves an issue where Suricata does not check the statistics of bypassed flows that have been timed out by workers.

Proposed Solution

I propose to solve this issue by forbidding workers from timing out capture-bypassed flows and allowing only FlowManager to handle them.

Changes:

  • Forbid workers from timing out capture-bypassed flows and having only FlowManager thread manage these flows.
  • This issue was originally part of Capture bypass stats gather v4 #15289, this PR separates it for clarity.

Links to ticket: 8442

Forbid worker to timeout capture-bypassed flows, as it does not have the
necessary components (BypassUpdate callback) to gather the necessary
statistics from the flows to make this decisions. Leave the
processing of bypass-capture flows only to FlowManager.

Ticket: 8442
@adaki4 adaki4 requested a review from victorjulien as a code owner May 7, 2026 09:12
@codecov
Copy link
Copy Markdown

codecov Bot commented May 7, 2026

Codecov Report

❌ Patch coverage is 75.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 82.64%. Comparing base (899e9f0) to head (8653de8).

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #15331      +/-   ##
==========================================
- Coverage   82.64%   82.64%   -0.01%     
==========================================
  Files         995      995              
  Lines      271075   271079       +4     
==========================================
- Hits       224042   224040       -2     
- Misses      47033    47039       +6     
Flag Coverage Δ
fuzzcorpus 61.04% <ø> (+<0.01%) ⬆️
livemode 18.41% <ø> (+0.02%) ⬆️
netns 22.61% <75.00%> (+0.01%) ⬆️
pcap 45.18% <ø> (-0.08%) ⬇️
suricata-verify 66.38% <ø> (-0.01%) ⬇️
unittests 58.57% <75.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant