Searched hist:"9 c75e168bc388094c04aabb6fc59c91abe06e81c" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/qemu/ |
| H A D | blockdev.c | diff 9c75e168bc388094c04aabb6fc59c91abe06e81c Wed Jun 25 15:55:30 CDT 2014 Jeff Cody <jcody@redhat.com> block: check for RESIZE blocker in the QMP command, not bdrv_truncate()
If we check for the RESIZE blocker in bdrv_truncate(), that means a
commit will fail if the overlay layer is larger than the base, due to
the backing blocker.
This is a regression in behavior from 2.0; currently, commit will try to
grow the size of the base image to match the overlay size, if the
overlay size is larger.
By moving this into the QMP command qmp_block_resize(), it allows
usage of bdrv_truncate() within block jobs.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|
| H A D | block.c | diff 9c75e168bc388094c04aabb6fc59c91abe06e81c Wed Jun 25 15:55:30 CDT 2014 Jeff Cody <jcody@redhat.com> block: check for RESIZE blocker in the QMP command, not bdrv_truncate()
If we check for the RESIZE blocker in bdrv_truncate(), that means a
commit will fail if the overlay layer is larger than the base, due to
the backing blocker.
This is a regression in behavior from 2.0; currently, commit will try to
grow the size of the base image to match the overlay size, if the
overlay size is larger.
By moving this into the QMP command qmp_block_resize(), it allows
usage of bdrv_truncate() within block jobs.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
|