diff options
author | Paolo Bonzini <pbonzini@redhat.com> | 2015-05-07 17:45:48 +0200 |
---|---|---|
committer | Stefan Hajnoczi <stefanha@redhat.com> | 2015-05-22 09:37:33 +0100 |
commit | eaf5fe2dd4ec001d645ff3b343f466457badaa64 (patch) | |
tree | e94748da892f0d825cb00b30c851a2d67afa4845 /block/vmdk.c | |
parent | fd0e60530f10078f488fa3e9591cc7db5732989c (diff) |
block: return EPERM on writes or discards to read-only devices
This is the behavior in the operating system, for example Linux's
blkdev_write_iter has the following:
if (bdev_read_only(I_BDEV(bd_inode)))
return -EPERM;
This does not apply to opening a device for read/write, when the
device only supports read-only operation. In this case any of
EACCES, EPERM or EROFS is acceptable depending on why writing is
not possible.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Message-id: 1431013548-22492-1-git-send-email-pbonzini@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'block/vmdk.c')
0 files changed, 0 insertions, 0 deletions