diff options
| author | Kevin Wolf <kwolf@redhat.com> | 2014-06-04 15:09:35 +0200 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2014-06-26 13:51:01 +0200 |
| commit | 8ee79e707a005c9274df7ce34265bb7d008b8cef (patch) | |
| tree | f8402fad14af55bef4457d8a5888db05d1d11fec /block/vmdk.c | |
| parent | 76c591b013782217cad67b35c74cd249e0413439 (diff) | |
block: Catch backing files assigned to non-COW drivers
Since we parse backing.* options to add a backing file from the command
line when the driver didn't assign one, it has been possible to have a
backing file for e.g. raw images (it just was never accessed).
This is obvious nonsense and should be rejected.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Diffstat (limited to 'block/vmdk.c')
| -rw-r--r-- | block/vmdk.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/block/vmdk.c b/block/vmdk.c index 83dd6fe4fb..d0de0193fc 100644 --- a/block/vmdk.c +++ b/block/vmdk.c @@ -2180,6 +2180,7 @@ static BlockDriver bdrv_vmdk = { .bdrv_detach_aio_context = vmdk_detach_aio_context, .bdrv_attach_aio_context = vmdk_attach_aio_context, + .supports_backing = true, .create_opts = &vmdk_create_opts, }; |