Fix race condition with cancellation tokens in Read/Flush operations … #61500
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 #59090 to release/6.0
Customer Impact
@AArnott reported a race condition with PipeReader where the ReadAsync operation could hang in some hard to reproduce cases when used with a cancellation token. The race resulting in hangs in various usages of pipelines in https://github.com/AArnott/Nerdbank.Streams (which is used in VS).
Testing
Manual testing. It's very hard to write a unit test for this scenario. Also verified by @AArnott
Risk
Low. The change was made to only affect a very narrow case (synchronous completion). Asserts were added to make sure existing invariants weren't broken.