From: Lukas Straub <lukasstraub2@web.de>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block <qemu-block@nongnu.org>,
Wen Congyang <wencongyang2@huawei.com>,
Xie Changlong <xiechanglong.d@gmail.com>,
Max Reitz <mreitz@redhat.com>
Subject: [PATCH v6 0/4] replication: Bugfix and properly attach children
Date: Sun, 18 Jul 2021 16:48:02 +0200 [thread overview]
Message-ID: <cover.1626619393.git.lukasstraub2@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]
Hello Everyone,
A while ago Kevin noticed that the replication driver doesn't properly attach
the children it wants to use. Instead, it directly copies the BdrvChilds from
it's backing file, which is wrong. Ths Patchset fixes the problem, fixes a
potential crash in replication_co_writev due to missing permissions and removes
a workaround that was put in place back then.
Tested with full COLO-migration setup in my COLO testsuite.
Regards,
Lukas Straub
Changes:
-v6:
-Drop "replication: Assert that children are writable"
-Added Reviewed-by tags
-v5:
-Assert that children are writable where it's needed
-v4:
-minor style fixes
-clarify why children areguaranteed to be writable in
"replication: Remove workaround"
-Added Reviewed-by tags
-v3:
-Split up into multiple patches
-Remove s->active_disk
-Clarify child permissions in commit message
-v2: Test for BDRV_CHILD_PRIMARY in replication_child_perm, since
bs->file might not be set yet. (Vladimir)
Lukas Straub (4):
replication: Remove s->active_disk
replication: Reduce usage of s->hidden_disk and s->secondary_disk
replication: Properly attach children
replication: Remove workaround
block/replication.c | 111 +++++++++++++++++++++++++++-----------------
1 file changed, 68 insertions(+), 43 deletions(-)
--
2.20.1
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2021-07-18 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-18 14:48 Lukas Straub [this message]
2021-07-18 14:48 ` [PATCH v6 1/4] replication: Remove s->active_disk Lukas Straub
2021-07-19 2:26 ` Zhang, Chen
2021-07-18 14:48 ` [PATCH v6 2/4] replication: Reduce usage of s->hidden_disk and s->secondary_disk Lukas Straub
2021-07-18 14:48 ` [PATCH v6 3/4] replication: Properly attach children Lukas Straub
2021-07-18 14:48 ` [PATCH v6 4/4] replication: Remove workaround Lukas Straub
2021-07-20 14:25 ` [PATCH v6 0/4] replication: Bugfix and properly attach children 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=cover.1626619393.git.lukasstraub2@web.de \
--to=lukasstraub2@web.de \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
--cc=wencongyang2@huawei.com \
--cc=xiechanglong.d@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).