diff options
| author | Daniel Verkamp <dverkamp@chromium.org> | 2020-01-15 12:57:33 -0800 |
|---|---|---|
| committer | Commit Bot <commit-bot@chromium.org> | 2020-01-24 20:22:49 +0000 |
| commit | 3c62aac88f829abd74cba7466e6a9e494af53b25 (patch) | |
| tree | 758ee4bd798acd877e04385d92b74b2c6ec94b23 /devices/src/virtio/gpu/mod.rs | |
| parent | 977f873a4140c29f838712e6f37137df4f0cd840 (diff) | |
| download | crosvm-3c62aac88f829abd74cba7466e6a9e494af53b25.tar crosvm-3c62aac88f829abd74cba7466e6a9e494af53b25.tar.gz crosvm-3c62aac88f829abd74cba7466e6a9e494af53b25.tar.bz2 crosvm-3c62aac88f829abd74cba7466e6a9e494af53b25.tar.lz crosvm-3c62aac88f829abd74cba7466e6a9e494af53b25.tar.xz crosvm-3c62aac88f829abd74cba7466e6a9e494af53b25.tar.zst crosvm-3c62aac88f829abd74cba7466e6a9e494af53b25.zip | |
devices: virtio: block: keep disk allocated on resize
When a non-sparse disk is resized, we should allocate storage for the newly-expanded space when the disk is grown to maintain the non-sparseness. To accomplish this, add a call to allocate in the resize function in the block device. BUG=chromium:858815 TEST=`crosvm disk resize ...` and verify disk image is fully allocated Change-Id: If263aa2b5c9da11b8bfc0586e4ac1575f2bd7084 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2015829 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org>
Diffstat (limited to 'devices/src/virtio/gpu/mod.rs')
0 files changed, 0 insertions, 0 deletions