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 0/9] block: Add auto-read-only option
Date: Wed, 17 Oct 2018 18:41:51 +0200 [thread overview]
Message-ID: <20181017164200.22344-1-kwolf@redhat.com> (raw)
See patch 2 for an explanation of the motivation.
v3:
- Clarified QAPI schema documentation that auto-read-only can only
degrade read-write to read-only, not the other way round [Eric]
- Don't refuse to set copy-on-read=on and auto-read-only=on at the same
time; only complain when actually trying to degrade to read-only
- Let bdrv_apply_auto_read_only() return -EACCESS on all errors
- Fixed file-posix and gluster implementations [Eric, Niels]
- Added a patch to make auto-read-only=on the default for human user
interfaces (-drive/-hda/...)
v2:
- Turn bdrv_set_read_only() into bdrv_apply_auto_read_only()
- Support the option in a lot more block drivers
Kevin Wolf (9):
block: Update flags in bdrv_set_read_only()
block: Add auto-read-only option
block: Require auto-read-only for existing fallbacks
nbd: Support auto-read-only option
file-posix: Support auto-read-only option
curl: Support auto-read-only option
gluster: Support auto-read-only option
iscsi: Support auto-read-only option
block: Make auto-read-only=on default for -drive
qapi/block-core.json | 7 ++++++
include/block/block.h | 5 +++-
block.c | 54 +++++++++++++++++++++++++++++++++++--------
block/bochs.c | 17 +++++---------
block/cloop.c | 16 ++++---------
block/curl.c | 8 +++----
block/dmg.c | 16 ++++---------
block/file-posix.c | 19 ++++++++++++---
block/gluster.c | 12 ++++++++--
block/iscsi.c | 8 ++++---
block/nbd-client.c | 10 ++++----
block/rbd.c | 14 ++++-------
block/vvfat.c | 11 +++------
blockdev.c | 1 +
14 files changed, 120 insertions(+), 78 deletions(-)
--
2.19.1
next reply other threads:[~2018-10-17 16:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 16:41 Kevin Wolf [this message]
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 ` [Qemu-devel] [PATCH v3 9/9] block: Make auto-read-only=on default for -drive Kevin Wolf
2018-10-17 19:10 ` 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-1-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).