Protect libcanard API calls within critical sections to prevent race conditions. #56
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
…e to follow that recommendation (and in fact isn't)
… implements the RAII-pattern around critical sections (automatic release of critical section lock when LockGuard object goes out of scope.
…ous access, therefore preventing race conditions and inconsistent data state
…as o1heap will only be called from within libcanard which in turn will only be called from within ArduinoUAVCAN which prevents multiple asynchronous access via critical sections.
aentinger
added
topic: firmware
aentinger
deleted the
protect-libcanard-api-calls-with-critical-section
branch
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.
This fixes #55.