-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix binary check expr is equal #1952
Conversation
Fix a bug in binary_check_expr::is_equal()--the comparison should also compare the operators in addition to both sides. Signed-off-by: Mark Stemm <mark.stemm@gmail.com>
Create two expressions with the same lhs/rhs but different ops, and ensure that is_equal() returns false. Signed-off-by: Mark Stemm <mark.stemm@gmail.com>
Perf diff from master - unit tests
Perf diff from master - scap file
Heap diff from master - unit tests
Heap diff from master - scap file
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. For an extra gold star, we could use a positive test (evt.num=0
is equal to evt.num = 0
)
LGTM label has been added. Git tree hash: 969c0d28bfd103dca403c0c7711ecdd916816512
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gnosek, jasondellaluce, mstemm The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/milestone 0.18.0 |
What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area libsinsp
/area tests
Does this PR require a change in the driver versions?
What this PR does / why we need it:
Fix a bug in
libsinsp::filter::ast::binary_check_expr::is_equal()
. The method should compare the operators but isn't. So an expressionevt.num >= 0
is mistakenly being considered equal toevt.num = 0
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: