diff options
| author | Vladimir Sementsov-Ogievskiy | 2022-07-26 22:11:28 +0200 |
|---|---|---|
| committer | Kevin Wolf | 2022-10-27 20:14:11 +0200 |
| commit | 4eba825a8237985dc1c53a42bc810dcfa1a3d5e3 (patch) | |
| tree | 87f25424bb91e0dd2d29721fe25fff6bb287496c /include | |
| parent | block/snapshot: stress that we fallback to primary child (diff) | |
| download | qemu-4eba825a8237985dc1c53a42bc810dcfa1a3d5e3.tar.gz qemu-4eba825a8237985dc1c53a42bc810dcfa1a3d5e3.tar.xz qemu-4eba825a8237985dc1c53a42bc810dcfa1a3d5e3.zip | |
Revert "block: Let replace_child_noperm free children"
We are going to reimplement this behavior (clear bs->file / bs->backing
pointers automatically when child->bs is cleared) in a nicer way, see
further commit
"block: Manipulate bs->file / bs->backing pointers in .attach/.detach".
With this revert we bring back a problem that was fixed by b0a9f6fed3d8.
Still the problem was mostly theoretical, we don't have concrete bugs
fixed by b0a9f6fed3d8, we don't have a specific test. Probably some
accidental failures of iotests are related.
Alternatively, we may merge this and following three reverts into final
"block: Manipulate ..." to avoid any kind of regression. But seems that
in this case having separate clear revert commits is better.
This reverts commit b0a9f6fed3d80de610dcd04a7e66f9f30a04174f.
Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Reviewed-by: Hanna Reitz <hreitz@redhat.com>
Message-Id: <20220726201134.924743-10-vsementsov@yandex-team.ru>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions