[release/7.0] Fixing memory ordering issue in ConcurrentQueue #78178
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.
Backport of #78142 to release/7.0
/cc @VSadov
Customer Impact
ToArray
/CopyTo
/Enumerate
operations on a ConcurrentQueue may fetch uninitialized data on arm64 under stress.Testing
regular tests. manual stress-testing of the targeted scenario.
Risk
Very Low. we were just missing a
Volatile.Read
to enforce the order of reads in one place.