diff options
author | Kevin Wolf <kwolf@redhat.com> | 2010-08-17 18:58:55 +0200 |
---|---|---|
committer | Kevin Wolf <kwolf@redhat.com> | 2010-08-30 18:29:22 +0200 |
commit | cdbae85169c384d1641aa1ae86cdeefe16285745 (patch) | |
tree | 16d9c8d11dfafdd0cfc7f572e46feec63c9b3f60 /qemu-img.c | |
parent | 010cb2b314f2fa629b6b0b8f2f73c9d562fff49f (diff) | |
download | qemu-cdbae85169c384d1641aa1ae86cdeefe16285745.tar.gz qemu-cdbae85169c384d1641aa1ae86cdeefe16285745.tar.bz2 qemu-cdbae85169c384d1641aa1ae86cdeefe16285745.zip |
qemu-img rebase: Open new backing file read-only
We never write to a backing file, so opening rw is useless. It just means that
you can't rebase on top of a file for which you don't have write permissions.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'qemu-img.c')
-rw-r--r-- | qemu-img.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/qemu-img.c b/qemu-img.c index e300f911cb..d2a978b912 100644 --- a/qemu-img.c +++ b/qemu-img.c @@ -1286,7 +1286,7 @@ static int img_rebase(int argc, char **argv) } bs_new_backing = bdrv_new("new_backing"); - ret = bdrv_open(bs_new_backing, out_baseimg, BDRV_O_FLAGS | BDRV_O_RDWR, + ret = bdrv_open(bs_new_backing, out_baseimg, BDRV_O_FLAGS, new_backing_drv); if (ret) { error("Could not open new backing file '%s'", out_baseimg); |