Fix cancellation race condition in PipeStream cancellation callback (#65909)
authorStephen Toub <stoub@microsoft.com>
Wed, 9 Mar 2022 11:49:16 +0000 (06:49 -0500)
committerGitHub <noreply@github.com>
Wed, 9 Mar 2022 11:49:16 +0000 (06:49 -0500)
commitca731545a58307870a0baebb0ee43eeea61f175f
tree171a9a9536a7a615b75a3dfd606b138fd600af07
parentf132942f1a490336cddc06f99abf38226bd9748e
Fix cancellation race condition in PipeStream cancellation callback (#65909)

* Fix cancellation race condition in PipeStream cancellation callback

The public PipeStream.SafePipeHandle property throws an exception if the handle has already been closed.  This code should have been using the internal InternalHandle property, which just gets the SafePipeHandle object if it exists.

* Update src/libraries/System.IO.Pipes/src/System/IO/Pipes/PipeStream.ValueTaskSource.cs

Co-authored-by: Adam Sitnik <adam.sitnik@gmail.com>
Co-authored-by: Adam Sitnik <adam.sitnik@gmail.com>
src/libraries/System.IO.Pipes/src/System/IO/Pipes/PipeStream.ValueTaskSource.cs