diff options
| author | Fam Zheng <famz@redhat.com> | 2014-06-24 20:26:36 +0800 |
|---|---|---|
| committer | Michael Roth <mdroth@linux.vnet.ibm.com> | 2014-08-07 03:50:04 -0500 |
| commit | 43ac708d4c021ade469d6e96e054abab4cb49e4b (patch) | |
| tree | 0ed1442291938868aae08f74d5f7605d22d16b89 /cpu-exec.c | |
| parent | 8e09e2013d82456f074b343d8505b25c0a159dce (diff) | |
| download | qemu-43ac708d4c021ade469d6e96e054abab4cb49e4b.tar.gz | |
mirror: Go through ready -> complete process for 0 len image
When mirroring or active committing a zero length image, BLOCK_JOB_READY
is not reported now, instead the job completes because we short circuit
the mirror job loop.
This is inconsistent with non-zero length images, and only confuses
management software.
Let's do the same thing when seeing a 0-length image: report ready
immediately; wait for block-job-cancel or block-job-complete; clear the
cancel flag as existing non-zero image synced case (cancelled after
ready); then jump to the exit.
Reported-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Fam Zheng <famz@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
(cherry picked from commit 9e48b025400b2d284e17860862b0a4aa02c6032d)
*removed dependency on bcada37b
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Diffstat (limited to 'cpu-exec.c')
0 files changed, 0 insertions, 0 deletions