Searched hist:"5 abbf0ee4d87c695deb1c3fca9bb994b93a3e3be" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 051 | diff 5abbf0ee4d87c695deb1c3fca9bb994b93a3e3be Thu Sep 18 04:48:34 CDT 2014 Kevin Wolf <kwolf@redhat.com> block: Catch simultaneous usage of options and their aliases
While thinking about precedence of conflicting block device options from
different sources, I noticed that you can specify both an option and its
legacy alias at the same time (e.g. readonly=on,read-only=off). Rather
than specifying the order of precedence, we should simply forbid such
combinations.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Benoît Canet <benoit.canet@nodalink.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
|
| H A D | 051.out | diff 5abbf0ee4d87c695deb1c3fca9bb994b93a3e3be Thu Sep 18 04:48:34 CDT 2014 Kevin Wolf <kwolf@redhat.com> block: Catch simultaneous usage of options and their aliases
While thinking about precedence of conflicting block device options from
different sources, I noticed that you can specify both an option and its
legacy alias at the same time (e.g. readonly=on,read-only=off). Rather
than specifying the order of precedence, we should simply forbid such
combinations.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Benoît Canet <benoit.canet@nodalink.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
|
| /openbmc/qemu/ |
| H A D | blockdev.c | diff 20d6cd47d0459bdc6a8b64e7abe8f713e0d4718e Wed Sep 24 00:45:27 CDT 2014 Jun Li <junmuzi@gmail.com> Modify qemu_opt_rename to realize renaming all items in opts
Add realization of rename all items in opts for qemu_opt_rename.
e.g:
When add bps twice in command line, need to rename all bps to
throttling.bps-total.
This patch solved following bug:
Bug 1145586 - qemu-kvm will give strange hint when add bps twice for a drive
ref:https://bugzilla.redhat.com/show_bug.cgi?id=1145586
[Resolved conflict with commit 5abbf0ee4d87c695deb1c3fca9bb994b93a3e3be
("block: Catch simultaneous usage of options and their aliases"). Check
for simultaneous use first, and then loop over all options.
--Stefan]
Signed-off-by: Jun Li <junmuzi@gmail.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Message-id: 1411537527-16715-1-git-send-email-junmuzi@gmail.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
diff 5abbf0ee4d87c695deb1c3fca9bb994b93a3e3be Thu Sep 18 04:48:34 CDT 2014 Kevin Wolf <kwolf@redhat.com> block: Catch simultaneous usage of options and their aliases
While thinking about precedence of conflicting block device options from
different sources, I noticed that you can specify both an option and its
legacy alias at the same time (e.g. readonly=on,read-only=off). Rather
than specifying the order of precedence, we should simply forbid such
combinations.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Benoît Canet <benoit.canet@nodalink.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
|