Dataset string memcap 3910/v12 #11281
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
Add a callback and helper function to handle data expiration. Update datasets to explicitly not use expiration.
In order to have access to the length of datatypes with variable lengths to correctly update memuse to calculate memcaps. Bug 3910
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #11281 +/- ##
==========================================
- Coverage 82.45% 77.63% -4.82%
==========================================
Files 961 961
Lines 251710 251774 +64
==========================================
- Hits 207552 195471 -12081
- Misses 44158 56303 +12145
Flags with carried forward coverage won't be shown. Click here to find out more. |
So far, when the data size was passed to the THash API, it was sent as a sizeof(Struct) which works fine for the other data types as they have a fixed length but not for the StringType. However, because of the sizeof construct, the length of a string type dataset was always taken to be 16 Bytes which is only the size of the struct itself. It did not accomodate the actual size of the string that the StringType holds. Fix this so that the memuse that is used to determine whether memcap was reached also takes into consideration the size of the actual string. Bug 3910
inashivb
force-pushed
the
dataset-string-memcap-3910/v12
branch
from
0e8c473
to
b08b661
Compare
|
Information: QA ran without warnings. Pipeline 21031 |
inashivb
force-pushed
the
dataset-string-memcap-3910/v12
branch
2 times, most recently
from
2bf9a69
to
1f24ae7
Compare
inashivb
force-pushed
the
dataset-string-memcap-3910/v12
branch
from
1f24ae7
to
7e5ee3a
Compare
|
Information: QA ran without warnings. Pipeline 21040 |
inashivb
force-pushed
the
dataset-string-memcap-3910/v12
branch
from
6a0b823
to
00bf0d2
Compare
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.
Link to redmine ticket: https://redmine.openinfosecfoundation.org/issues/3910
Previous PR: #11251
Changes since v11:
SV_BRANCH=OISF/suricata-verify#1906