From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
qemu-block@nongnu.org
Subject: [Qemu-devel] [PATCH 2/4] block: Fix write flags in bdrv_backing_options
Date: Fri, 9 Mar 2018 16:09:08 +0800 [thread overview]
Message-ID: <20180309080910.7274-3-famz@redhat.com> (raw)
In-Reply-To: <20180309080910.7274-1-famz@redhat.com>
When the child in question already has write access, we shouldn't change
that just because the parent being open/reopen doesn't need it. But if
we are inherenting the flags from a writable parent, we shouldn't copy
the BDRV_O_RDWR flag, which is consistent with the BDRV_OPT_READ_ONLY
option we set.
Signed-off-by: Fam Zheng <famz@redhat.com>
---
block.c | 15 +++++++++++----
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/block.c b/block.c
index bedbe208e6..937f9fe159 100644
--- a/block.c
+++ b/block.c
@@ -997,7 +997,10 @@ static void bdrv_backing_options(int *child_flags, QDict *child_options,
int parent_flags, QDict *parent_options,
int current_flags)
{
- int flags = parent_flags;
+ /* write flag should be preserved if the backing file already has it. This
+ * is important during reopen, to keep "parallel block jobs" work. */
+ int write_flag = current_flags & BDRV_O_RDWR;
+ int flags = parent_flags | write_flag;
/* The cache mode is inherited unmodified for backing files; except WCE,
* which is only applied on the top level (BlockBackend) */
@@ -1005,9 +1008,13 @@ static void bdrv_backing_options(int *child_flags, QDict *child_options,
qdict_copy_default(child_options, parent_options, BDRV_OPT_CACHE_NO_FLUSH);
qdict_copy_default(child_options, parent_options, BDRV_OPT_FORCE_SHARE);
- /* backing files always opened read-only */
- qdict_set_default_str(child_options, BDRV_OPT_READ_ONLY, "on");
- flags &= ~BDRV_O_COPY_ON_READ;
+
+ if (!write_flag) {
+ flags &= ~BDRV_O_COPY_ON_READ;
+ /* backing files always opened read-only */
+ qdict_set_default_str(child_options, BDRV_OPT_READ_ONLY, "on");
+ flags &= ~BDRV_O_RDWR;
+ }
/* snapshot=on is handled on the top layer */
flags &= ~(BDRV_O_SNAPSHOT | BDRV_O_TEMPORARY);
--
2.14.3
next prev parent reply other threads:[~2018-03-09 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 8:09 [Qemu-devel] [PATCH 0/4] block: Fix permission during reopen Fam Zheng
2018-03-09 8:09 ` [Qemu-devel] [PATCH 1/4] block: Pass "current_flags" in BdrvChildRole.inherit_options Fam Zheng
2018-03-09 8:09 ` Fam Zheng [this message]
2018-03-09 8:09 ` [Qemu-devel] [PATCH 3/4] block: Use the actual current_flags during reopen Fam Zheng
2018-03-09 8:09 ` [Qemu-devel] [PATCH 4/4] iotests: Add regression test for commit base locking Fam Zheng
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=20180309080910.7274-3-famz@redhat.com \
--to=famz@redhat.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 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).