RefArch: make RA_stop_signal_called atomic Avoid a data race between … - #3
Open
shadowfaxx1 wants to merge 1 commit into
Open
RefArch: make RA_stop_signal_called atomic Avoid a data race between …#3shadowfaxx1 wants to merge 1 commit into
shadowfaxx1 wants to merge 1 commit into
Conversation
…RX/TX threads and the signal handler.
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
1 participant
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.
Description
Replace
RA_stop_signal_calledwithstd::atomic<bool>inRefArch.The stop flag is accessed by multiple RX/TX threads and modified by
the signal handler during shutdown. Using an atomic flag avoids a
potential data race while preserving existing behavior.
Related Issue
N/A
Which devices/areas does this affect?
Testing Done
Checklist