fix(userspace/falco): fix watchdog race condition on timeout exchange#3820
Merged
poiana merged 1 commit intofalcosecurity:masterfrom Mar 12, 2026
Merged
Conversation
The watchdog thread and stop() consume the timeout pointer with m_timeout.exchange(nullptr, ...). That exchange was using memory_order_release. The load part of the RMW needs acquire semantics so it synchronizes-with the release store in set_timeout()/cancel_timeout(); otherwise the consumer can see the pointer value without seeing the writes that initialized the timeout_data and payload (data race). Use memory_order_acq_rel on the consumer exchanges so the load synchronizes-with the producer and the pointed-to memory is visible before use. Signed-off-by: irozzo-1A <[email protected]>
leogr
approved these changes
Mar 12, 2026
Member
leogr
left a comment
There was a problem hiding this comment.
Very good catch. The bug has been here since 2020.
The fix LGTM!
Contributor
|
LGTM label has been added. DetailsGit tree hash: 93cab89060b1b4a4fc5f778a3895cb0d70ef92a7 |
Member
|
/milestone 0.44.0 |
sgaist
approved these changes
Mar 12, 2026
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: irozzo-1A, leogr, sgaist The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This file contains hidden or 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
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.
What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
What this PR does / why we need it:
The watchdog thread and stop() consume the timeout pointer with
m_timeout.exchange(nullptr, ...). That exchange was using memory_order_release. The load part of the RMW needs acquire semantics so it synchronizes-with the release store inset_timeout()/cancel_timeout();otherwise the consumer can see the pointer value without seeing the writes that initialized the timeout_data and payload (data race).Use
memory_order_acq_relon the consumer exchanges so the load synchronizes-with the producer and the pointed-to memory is visible before use.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: