From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 3/4] block/copy-on-read: Fix permissions for inactive node
Date: Tue, 30 Jul 2019 13:24:24 +0200 [thread overview]
Message-ID: <20190730112425.21497-4-kwolf@redhat.com> (raw)
In-Reply-To: <20190730112425.21497-1-kwolf@redhat.com>
The copy-on-read drive must not request the WRITE_UNCHANGED permission
for its child if the node is inactive, otherwise starting a migration
destination with -incoming will fail because the child cannot provide
write access yet:
qemu-system-x86_64: -blockdev copy-on-read,file=img,node-name=cor: Block node is read-only
Earlier QEMU versions additionally ran into an abort() on the migration
source side: bdrv_inactivate_recurse() failed to update permissions.
This is silently ignored today because it was only supposed to loosen
restrictions. This is the symptom that was originally reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=1733022
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
---
block/copy-on-read.c | 16 +++++++---------
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git a/block/copy-on-read.c b/block/copy-on-read.c
index 22f24fd0db..6631f30205 100644
--- a/block/copy-on-read.c
+++ b/block/copy-on-read.c
@@ -56,16 +56,14 @@ static void cor_child_perm(BlockDriverState *bs, BdrvChild *c,
uint64_t perm, uint64_t shared,
uint64_t *nperm, uint64_t *nshared)
{
- if (c == NULL) {
- *nperm = (perm & PERM_PASSTHROUGH) | BLK_PERM_WRITE_UNCHANGED;
- *nshared = (shared & PERM_PASSTHROUGH) | PERM_UNCHANGED;
- return;
- }
+ *nperm = perm & PERM_PASSTHROUGH;
+ *nshared = (shared & PERM_PASSTHROUGH) | PERM_UNCHANGED;
- *nperm = (perm & PERM_PASSTHROUGH) |
- (c->perm & PERM_UNCHANGED);
- *nshared = (shared & PERM_PASSTHROUGH) |
- (c->shared_perm & PERM_UNCHANGED);
+ /* We must not request write permissions for an inactive node, the child
+ * cannot provide it. */
+ if (!(bs->open_flags & BDRV_O_INACTIVE)) {
+ *nperm |= BLK_PERM_WRITE_UNCHANGED;
+ }
}
--
2.20.1
next prev parent reply other threads:[~2019-07-30 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 11:24 [Qemu-devel] [PULL 0/4] Block layer and multiboot test patches Kevin Wolf
2019-07-30 11:24 ` [Qemu-devel] [PULL 1/4] tests/multiboot: Fix load address of test kernels Kevin Wolf
2019-07-30 11:24 ` [Qemu-devel] [PULL 2/4] Fixes: add read-zeroes to 051.out Kevin Wolf
2019-07-30 11:24 ` Kevin Wolf [this message]
2019-07-30 11:24 ` [Qemu-devel] [PULL 4/4] scsi-cd: Fix inserting read-only media in empty drive Kevin Wolf
2019-07-30 12:27 ` [Qemu-devel] [PULL 0/4] Block layer and multiboot test patches Peter Maydell
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=20190730112425.21497-4-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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).