Handle IOV_MAX limit in RandomAccess #109340
Merged
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.
We were not respecting IOV_MAX in
pwritevandpreadvexposed byRandomAccess. After writing test for it I've realized that the logic for handling the incomplete writes was also incomplete (please see the changes in managed layer).fixes #108383 and adds a test for scenario described in #108322 , so I can backport #108380 to all supported versions.