Searched hist:"54 a32bfec140e03ebb19863db944b1c81e4df25e" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/qemu/include/block/ |
| H A D | block.h | diff 54a32bfec140e03ebb19863db944b1c81e4df25e Thu Aug 03 10:02:58 CDT 2017 Kevin Wolf <kwolf@redhat.com> block: Allow reopen rw without BDRV_O_ALLOW_RDWR
BDRV_O_ALLOW_RDWR is a flag that tells whether qemu can internally
reopen a node read-write temporarily because the user requested
read-write for the top-level image, but qemu decided that read-only is
enough for this node (a backing file).
bdrv_reopen() is different, it is also used for cases where the user
changed their mind and wants to update the options. There is no reason
to forbid making a node read-write in that case.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Jeff Cody <jcody@redhat.com>
Reviewed-by: John Snow <jsnow@redhat.com>
|
| /openbmc/qemu/ |
| H A D | block.c | diff 54a32bfec140e03ebb19863db944b1c81e4df25e Thu Aug 03 10:02:58 CDT 2017 Kevin Wolf <kwolf@redhat.com> block: Allow reopen rw without BDRV_O_ALLOW_RDWR
BDRV_O_ALLOW_RDWR is a flag that tells whether qemu can internally
reopen a node read-write temporarily because the user requested
read-write for the top-level image, but qemu decided that read-only is
enough for this node (a backing file).
bdrv_reopen() is different, it is also used for cases where the user
changed their mind and wants to update the options. There is no reason
to forbid making a node read-write in that case.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Jeff Cody <jcody@redhat.com>
Reviewed-by: John Snow <jsnow@redhat.com>
|