Searched hist:"8 ee79e707a005c9274df7ce34265bb7d008b8cef" (Results 1 – 8 of 8) sorted by relevance
/openbmc/qemu/tests/qemu-iotests/ |
H A D | 051 | diff 8ee79e707a005c9274df7ce34265bb7d008b8cef Wed Jun 04 08:09:35 CDT 2014 Kevin Wolf <kwolf@redhat.com> 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>
|
H A D | 051.out | diff 8ee79e707a005c9274df7ce34265bb7d008b8cef Wed Jun 04 08:09:35 CDT 2014 Kevin Wolf <kwolf@redhat.com> 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>
|
/openbmc/qemu/block/ |
H A D | qcow.c | diff 8ee79e707a005c9274df7ce34265bb7d008b8cef Wed Jun 04 08:09:35 CDT 2014 Kevin Wolf <kwolf@redhat.com> 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>
|
H A D | qed.c | diff 8ee79e707a005c9274df7ce34265bb7d008b8cef Wed Jun 04 08:09:35 CDT 2014 Kevin Wolf <kwolf@redhat.com> 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>
|
H A D | vmdk.c | diff 8ee79e707a005c9274df7ce34265bb7d008b8cef Wed Jun 04 08:09:35 CDT 2014 Kevin Wolf <kwolf@redhat.com> 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>
|
H A D | qcow2.c | diff 8ee79e707a005c9274df7ce34265bb7d008b8cef Wed Jun 04 08:09:35 CDT 2014 Kevin Wolf <kwolf@redhat.com> 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>
|
/openbmc/qemu/include/block/ |
H A D | block_int.h | diff 8ee79e707a005c9274df7ce34265bb7d008b8cef Wed Jun 04 08:09:35 CDT 2014 Kevin Wolf <kwolf@redhat.com> 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>
|
/openbmc/qemu/ |
H A D | block.c | diff 8ee79e707a005c9274df7ce34265bb7d008b8cef Wed Jun 04 08:09:35 CDT 2014 Kevin Wolf <kwolf@redhat.com> 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>
|