From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, mreitz@redhat.com, kwolf@redhat.com,
berto@igalia.com, vsementsov@virtuozzo.com
Subject: [PATCH v6 0/9] Allow changing bs->file on reopen
Date: Thu, 10 Jun 2021 15:05:28 +0300 [thread overview]
Message-ID: <20210610120537.196183-1-vsementsov@virtuozzo.com> (raw)
Note that this is only "subject" part of original Alberto's
"[PATCH v4 0/6] Allow changing bs->file on reopen" which also included
multiple reopen and dropping x- prefix of reopen together with some
refactoring.
v6: rebased
08: changed error message in test
09: somehow, now '.' are spread in test output
Now, v6 based on two first simple patches of
"[PATCH v5 00/35] block: publish backup-top filter"
Based-on: <20210610112618.127378-1-vsementsov@virtuozzo.com>
So, if this goes first, just take first two patches of
"[PATCH v5 00/35] block: publish backup-top filter" which are already
reviewed by Max.
v5:
1-7: new
8: changed a lot
9: unchanged
Alberto Garcia (2):
block: Allow changing bs->file on reopen
iotests: Test replacing files with x-blockdev-reopen
Vladimir Sementsov-Ogievskiy (7):
block: introduce bdrv_remove_file_or_backing_child()
block: introduce bdrv_set_file_or_backing_noperm()
block: bdrv_reopen_parse_backing(): don't check aio context
block: bdrv_reopen_parse_backing(): don't check frozen child
block: bdrv_reopen_parse_backing(): simplify handling implicit filters
block: move supports_backing check to
bdrv_set_file_or_backing_noperm()
block: BDRVReopenState: drop replace_backing_bs field
include/block/block.h | 2 +-
block.c | 286 ++++++++++++++++---------------
tests/unit/test-bdrv-drain.c | 1 +
tests/unit/test-bdrv-graph-mod.c | 1 +
tests/qemu-iotests/245 | 140 +++++++++++++--
tests/qemu-iotests/245.out | 11 +-
6 files changed, 287 insertions(+), 154 deletions(-)
--
2.29.2
next reply other threads:[~2021-06-10 12:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 12:05 Vladimir Sementsov-Ogievskiy [this message]
2021-06-10 12:05 ` [PATCH v6 1/9] block: introduce bdrv_remove_file_or_backing_child() Vladimir Sementsov-Ogievskiy
2021-06-10 12:05 ` [PATCH v6 2/9] block: introduce bdrv_set_file_or_backing_noperm() Vladimir Sementsov-Ogievskiy
2021-06-10 12:05 ` [PATCH v6 3/9] block: bdrv_reopen_parse_backing(): don't check aio context Vladimir Sementsov-Ogievskiy
2021-06-10 12:05 ` [PATCH v6 4/9] block: bdrv_reopen_parse_backing(): don't check frozen child Vladimir Sementsov-Ogievskiy
2021-06-10 12:05 ` [PATCH v6 5/9] block: bdrv_reopen_parse_backing(): simplify handling implicit filters Vladimir Sementsov-Ogievskiy
2021-06-10 12:05 ` [PATCH v6 6/9] block: move supports_backing check to bdrv_set_file_or_backing_noperm() Vladimir Sementsov-Ogievskiy
2021-06-10 12:05 ` [PATCH v6 7/9] block: BDRVReopenState: drop replace_backing_bs field Vladimir Sementsov-Ogievskiy
2021-06-10 12:05 ` [PATCH v6 8/9] block: Allow changing bs->file on reopen Vladimir Sementsov-Ogievskiy
2021-06-10 12:05 ` [PATCH v6 9/9] iotests: Test replacing files with x-blockdev-reopen Vladimir Sementsov-Ogievskiy
2021-06-28 15:39 ` [PATCH v6 0/9] Allow changing bs->file on reopen Kevin Wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210610120537.196183-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.