qemu-e2k/tests/qemu-iotests/029.out

QA output created by 029

Test loading internal snapshots where the L1 table of the snapshot
is smaller than the current L1 table.

Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864 
wrote 4096/4096 bytes at offset 0
4 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
No errors were found on the image.
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=16777216 
wrote 4194304/4194304 bytes at offset 0
4 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
No errors were found on the image.

Try using a huge VM state

Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864 
wrote 4096/4096 bytes at offset 1099511627776
4 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
read 4096/4096 bytes at offset 1099511627776
4 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
No errors were found on the image.

qcow2_snapshot_load_tmp() should take the L1 size from the snapshot

Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864 
*** done
qemu-iotests: test loading internal snapshots Test loading internal snapshots where the L1 table of the snapshot is smaller than the current L1 table. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Signed-off-by: Christoph Hellwig <hch@lst.de> 2011-08-05 16:37:25 +02:00			`QA output created by 029`
qcow2: Fix copy_sectors() with VM state bs->total_sectors is not the highest possible sector number that could be involved in a copy on write operation: VM state is after the end of the virtual disk. This resulted in wrong values for the number of sectors to be copied (n). The code that checks for the end of the image isn't required any more because the code hasn't been calling the block layer's bdrv_read() for a long time; instead, it directly calls qcow2_readv(), which doesn't error out on VM state sector numbers. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Reviewed-by: Max Reitz <mreitz@redhat.com> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> 2014-03-26 13:06:03 +01:00
			`Test loading internal snapshots where the L1 table of the snapshot`
			`is smaller than the current L1 table.`

qemu-iotests: Always filter cluster_size out in _make_test_img Some image formats do have a cluster size, others don't, but there are tests that work with both sets of images and currently we get failures because the qemu-img create output doesn't mention the cluster size for some formats. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com> 2012-04-11 11:21:25 +02:00			`Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864`
qemu-iotests: test loading internal snapshots Test loading internal snapshots where the L1 table of the snapshot is smaller than the current L1 table. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Signed-off-by: Christoph Hellwig <hch@lst.de> 2011-08-05 16:37:25 +02:00			`wrote 4096/4096 bytes at offset 0`
			`4 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)`
			`No errors were found on the image.`
qemu-iotests: Always filter cluster_size out in _make_test_img Some image formats do have a cluster size, others don't, but there are tests that work with both sets of images and currently we get failures because the qemu-img create output doesn't mention the cluster size for some formats. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com> 2012-04-11 11:21:25 +02:00			`Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=16777216`
qemu-iotests: test loading internal snapshots Test loading internal snapshots where the L1 table of the snapshot is smaller than the current L1 table. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Signed-off-by: Christoph Hellwig <hch@lst.de> 2011-08-05 16:37:25 +02:00			`wrote 4194304/4194304 bytes at offset 0`
			`4 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)`
			`No errors were found on the image.`
qcow2: Fix copy_sectors() with VM state bs->total_sectors is not the highest possible sector number that could be involved in a copy on write operation: VM state is after the end of the virtual disk. This resulted in wrong values for the number of sectors to be copied (n). The code that checks for the end of the image isn't required any more because the code hasn't been calling the block layer's bdrv_read() for a long time; instead, it directly calls qcow2_readv(), which doesn't error out on VM state sector numbers. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Reviewed-by: Max Reitz <mreitz@redhat.com> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> 2014-03-26 13:06:03 +01:00
			`Try using a huge VM state`

			`Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864`
			`wrote 4096/4096 bytes at offset 1099511627776`
			`4 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)`
			`read 4096/4096 bytes at offset 1099511627776`
			`4 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)`
			`No errors were found on the image.`
qcow2: Fix L1 allocation size in qcow2_snapshot_load_tmp() (CVE-2014-0145) For the L1 table to loaded for an internal snapshot, the code allocated only enough memory to hold the currently active L1 table. If the snapshot's L1 table is actually larger than the current one, this leads to a buffer overflow. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Reviewed-by: Max Reitz <mreitz@redhat.com> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com> 2014-03-26 13:06:05 +01:00
			`qcow2_snapshot_load_tmp() should take the L1 size from the snapshot`

			`Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=67108864`
qemu-iotests: test loading internal snapshots Test loading internal snapshots where the L1 table of the snapshot is smaller than the current L1 table. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Signed-off-by: Christoph Hellwig <hch@lst.de> 2011-08-05 16:37:25 +02:00			`*** done`