Searched hist:"67251 a311371c4d22e803f151f47fe817175b6c3" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/qemu/block/ |
| H A D | vmdk.c | diff 67251a311371c4d22e803f151f47fe817175b6c3 Thu Apr 09 11:54:04 CDT 2015 Kevin Wolf <kwolf@redhat.com> block: Fix reopen flag inheritance
When reopening an image, the block layer already takes care to reopen
bs->file as well with recalculated inherited flags. The same must happen
for any other child (most notably missing before this patch: backing
files).
If bs->file (or any other child) didn't originally inherit from bs, e.g.
because it was created separately and then only referenced, it must not
inherit flags on reopen either, so check the inherited_from field before
propagation the reopen down.
VMDK already reopened its extents manually; this code can now be
dropped.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
|
| /openbmc/qemu/ |
| H A D | block.c | diff 67251a311371c4d22e803f151f47fe817175b6c3 Thu Apr 09 11:54:04 CDT 2015 Kevin Wolf <kwolf@redhat.com> block: Fix reopen flag inheritance
When reopening an image, the block layer already takes care to reopen
bs->file as well with recalculated inherited flags. The same must happen
for any other child (most notably missing before this patch: backing
files).
If bs->file (or any other child) didn't originally inherit from bs, e.g.
because it was created separately and then only referenced, it must not
inherit flags on reopen either, so check the inherited_from field before
propagation the reopen down.
VMDK already reopened its extents manually; this code can now be
dropped.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
|