From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, mreitz@redhat.com, eblake@redhat.com,
pkrempa@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v3 9/9] block: Make auto-read-only=on default for -drive
Date: Wed, 17 Oct 2018 18:42:00 +0200 [thread overview]
Message-ID: <20181017164200.22344-10-kwolf@redhat.com> (raw)
In-Reply-To: <20181017164200.22344-1-kwolf@redhat.com>
While we want machine interfaces like -blockdev and QMP blockdev-add to
add as little auto-detection as possible so that management tools are
explicit about their needs, -drive is a convenience option for human
users. Enabling auto-read-only=on by default there enables users to use
read-only images for read-only guest devices without having to specify
read-only=on explicitly. If they try to attach the image to a read-write
device, they will still get an error message.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
---
blockdev.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/blockdev.c b/blockdev.c
index a8755bd908..ab57a8a53a 100644
--- a/blockdev.c
+++ b/blockdev.c
@@ -590,6 +590,7 @@ static BlockBackend *blockdev_init(const char *file, QDict *bs_opts,
qdict_set_default_str(bs_opts, BDRV_OPT_CACHE_NO_FLUSH, "off");
qdict_set_default_str(bs_opts, BDRV_OPT_READ_ONLY,
read_only ? "on" : "off");
+ qdict_set_default_str(bs_opts, BDRV_OPT_AUTO_READ_ONLY, "on");
assert((bdrv_flags & BDRV_O_CACHE_MASK) == 0);
if (runstate_check(RUN_STATE_INMIGRATE)) {
--
2.19.1
next prev parent reply other threads:[~2018-10-17 16:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 16:41 [Qemu-devel] [PATCH v3 0/9] block: Add auto-read-only option Kevin Wolf
2018-10-17 16:41 ` [Qemu-devel] [PATCH v3 1/9] block: Update flags in bdrv_set_read_only() Kevin Wolf
2018-10-17 16:41 ` [Qemu-devel] [PATCH v3 2/9] block: Add auto-read-only option Kevin Wolf
2018-10-17 18:44 ` Eric Blake
2018-10-17 16:41 ` [Qemu-devel] [PATCH v3 3/9] block: Require auto-read-only for existing fallbacks Kevin Wolf
2018-10-17 18:53 ` Eric Blake
2018-10-18 13:23 ` Kevin Wolf
2018-10-17 16:41 ` [Qemu-devel] [PATCH v3 4/9] nbd: Support auto-read-only option Kevin Wolf
2018-10-17 16:41 ` [Qemu-devel] [PATCH v3 5/9] file-posix: " Kevin Wolf
2018-10-17 19:07 ` Eric Blake
2018-10-17 16:41 ` [Qemu-devel] [PATCH v3 6/9] curl: " Kevin Wolf
2018-10-17 16:41 ` [Qemu-devel] [PATCH v3 7/9] gluster: " Kevin Wolf
2018-10-17 18:33 ` [Qemu-devel] [Qemu-block] " Niels de Vos
2018-10-17 16:41 ` [Qemu-devel] [PATCH v3 8/9] iscsi: " Kevin Wolf
2018-10-17 16:42 ` Kevin Wolf [this message]
2018-10-17 19:10 ` [Qemu-devel] [PATCH v3 9/9] block: Make auto-read-only=on default for -drive Eric Blake
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=20181017164200.22344-10-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=mreitz@redhat.com \
--cc=pkrempa@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).