| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
* add test for Int32 overflow for WriteGather in RandomAccess * add failing test fore more than IOV_MAX buffers * fix both the native and managed parts --------- Co-authored-by: Adeel Mujahid <3840695+am11@users.noreply.github.com> Co-authored-by: Stephen Toub <stoub@microsoft.com>
|
Tagging subscribers to this area: @dotnet/area-system-io |
Sorry, something went wrong.
|
/azp list |
Sorry, something went wrong.
Sorry, something went wrong.
|
/azp run runtime-libraries-coreclr outerloop |
Sorry, something went wrong.
|
Azure Pipelines successfully started running 1 pipeline(s). |
Sorry, something went wrong.
|
@adamsitnik did you want to port the same test fixes to this PR that you mentioned in #109648? |
Sorry, something went wrong.
|
Sorry, something went wrong.
|
Ok, please add back servicing-consider when it's ready. |
Sorry, something went wrong.
* don't run these tests in parallel, as each test cases uses more than 4 GB ram and disk! * fix the test: handle incomplete reads that should happen when we hit the max buffer limit * incomplete write fix: - pin the buffers only once - when re-trying, do that only for the actual reminder * Use native memory to get OOM a soon as we run out of memory (hoping to avoid the process getting killed on Linux when OOM happens) * For macOS preadv and pwritev can fail with EINVAL when the total length of all vectors overflows a 32-bit integer. * add an assert that is going to warn us if vector.Count is ever more than Int32.MaxValue --------- Co-authored-by: Michał Petryka <35800402+MichalPetryka@users.noreply.github.com>
|
/azp run runtime-libraries-coreclr outerloop |
Sorry, something went wrong.
|
Azure Pipelines successfully started running 1 pipeline(s). |
Sorry, something went wrong.
|
@adamsitnik Friendly reminder that code complete is on April 14th for the May Release. If you'd like to get this change included in that release, please get a Tactics approval and merge this PR before that date. |
Sorry, something went wrong.
|
@adamsitnik friendly reminder that code complete is on Monday May 12th (2:00 PM Pacific) for the June Release. If you'd like to get this change included in that release, please get a Tactics approval and merge this PR before the deadline. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Backport of #108380 and #109340 and #109826 to release/9.0-staging
Customer Impact
Customers using RandomAccess.Write overload that accepts multiple buffers have observed IOException being thrown in two scenarios:
When I was fixing #108383 I've realized that the logic for handling incomplete writes has a bug.
For incomplete multi-buffer writes, the API was not reporting any exceptions. It returns void, so it should write everything or throw an exception.
Regression
We had all 3 bugs since the API was introduced (.NET 6).
Testing
New unit tests were added. They were failing before the fix were applied. They are passing now.
Risk
Low, the fix is simple and covered with tests.