diff options
| author | Daniel Verkamp <dverkamp@chromium.org> | 2018-09-06 10:09:31 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2018-09-21 00:51:15 -0700 |
| commit | a40cbb4a948ea826f69cb83728c31a5a253a3b1c (patch) | |
| tree | cbfa493a310fbf54b98957222aa9e85ed10b56cf /kokoro | |
| parent | a0408258e09c406324ddae0aa5c30a7b75d04e31 (diff) | |
| download | crosvm-a40cbb4a948ea826f69cb83728c31a5a253a3b1c.tar crosvm-a40cbb4a948ea826f69cb83728c31a5a253a3b1c.tar.gz crosvm-a40cbb4a948ea826f69cb83728c31a5a253a3b1c.tar.bz2 crosvm-a40cbb4a948ea826f69cb83728c31a5a253a3b1c.tar.lz crosvm-a40cbb4a948ea826f69cb83728c31a5a253a3b1c.tar.xz crosvm-a40cbb4a948ea826f69cb83728c31a5a253a3b1c.tar.zst crosvm-a40cbb4a948ea826f69cb83728c31a5a253a3b1c.zip | |
devices: block: enforce read-only in execute()
To fully meet the requirements laid out by the virtio specification, we need to fail write commands for devices that expose VIRTIO_BLK_F_RO with a specific error code of VIRTIO_BLK_S_IOERR. Pipe the read_only status down into the worker and the request execute function so that it can be checked and return the correct error code. BUG=chromium:872973 TEST=Attempt to write to read-only /dev/vda in termina Change-Id: I98c8ad17fde497e5a529d9e65096fb4ef022fd65 Signed-off-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1211062 Reviewed-by: Stephen Barber <smbarber@chromium.org>
Diffstat (limited to 'kokoro')
0 files changed, 0 insertions, 0 deletions