disk_*: handle out of range accesses #415
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.
Currently, the SCSI and NVMe emulators validate that a read/write/unmap is in range before calling down to the backing disks. This creates a TOCTOU problem because the disk size can change at any time, asynchronously from any IO. It also creates additional synchronization headaches since the disk implementations must be able to provide the up-to-date disk size efficiently.
As a first step, add this range checking in the various disk implementations. A subsequent change can remove the redundant checks in the NVMe and SCSI emulators.