flow/manager: fix multi instance row tracking #12205
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In multi instance flow manager setups, each flow manager gets a slice of the hash table to manage. Due to a logic error in the chunked scanning of the hash slice, instances beyond the first would always rescan the same subslice of their slice. The `pos` variable that is used to keep the state of what the starting position for the next scan was supposed to be was treated as if it held a relative value. Relative to the bounds of the slice. It was however, holding an absolute position. This meant that when doing it's bounds check it was always considered out of bounds. This patch addresses the issue by correctly handling the fact that the value is absolute. Bug: OISF#7365.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #12205 +/- ##
==========================================
- Coverage 83.17% 83.17% -0.01%
==========================================
Files 912 912
Lines 257111 257111
==========================================
- Hits 213856 213851 -5
- Misses 43255 43260 +5
Flags with carried forward coverage won't be shown. Click here to find out more. |
|
Replaced by #12208 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In multi instance flow manager setups, each flow manager gets a slice of the hash table to manage. Due to a logic error in the chunked scanning of the hash slice, instances beyond the first would always rescan the same subslice of their slice.
The
posvariable that is used to keep the state of what the starting position for the next scan was supposed to be was treated as if it held a relative value. Relative to the bounds of the slice. It was however, holding an absolute position. This meant that when doing it's bounds check it was always considered out of bounds.This patch addresses the issue by correctly handling the fact that the value is absolute.
Bug: #7365.
https://redmine.openinfosecfoundation.org/issues/7365