fix(pkg/cgo): solve data races when assigning/deleting and accessing handles #85
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 plugin-sdk
What this PR does / why we need it:
Due to how shared object loading works in Linux and in the falcosecurity libs, I discovered that concurrent (and legitimate, as per generalized non-Falco libs consumers) operations to plugins written in Go led to panics and segfaults caused by data races in case of many workers.
So far my research led to discovering that this kind of issues disappear when re-working the
cgo.Handle
primitives to support proper synchronization.Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?: