fix(userspace/falco): use given priority in falco_outputs::handle_msg() #1450
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.
What type of PR is this?
/kind bug
/kind cleanup
Any specific area of the project related to this PR?
/area engine
What this PR does / why we need it:
Hardcoded values (
Critical
) for message's priority were present infalco_outputs::handle_msg()
:falco/userspace/falco/falco_outputs.cpp
Line 206 in 47fa7d5
falco/userspace/falco/falco_outputs.cpp
Line 219 in 47fa7d5
Although that was no problem because
handle_msg()
is being used only for drop alerts that are always emitted withCritical
priority level, it can lead to errors in the future.Moreover,
handle_msg()
has apriority
field already in its signature andsyscall_evt_drop_mgr
is already passing the expected value:falco/userspace/falco/event_drops.cpp
Lines 138 to 144 in 47fa7d5
So, this PR corrects the
handle_msg()
implementation to use the given priority.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Since
handle_msg()
is only called withinsyscall_evt_drop_mgr
and the outputted priority value is not changed, this PR does not introduce any user-facing change.Somehow related to #1417
Does this PR introduce a user-facing change?: