From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: [PATCH v2 0/2] qemu-img convert: Unshare write permission for source
Date: Thu, 22 Apr 2021 18:43:42 +0200 [thread overview]
Message-ID: <20210422164344.283389-1-kwolf@redhat.com> (raw)
v2:
- Still share BLK_PERM_CONSISTENT_READ. It doesn't hurt users that don't
want their image modified in parallel and it fixes some use cases
covered by iotests.
Kevin Wolf (2):
block: Add BDRV_O_NO_SHARE for blk_new_open()
qemu-img convert: Unshare write permission for source
include/block/block.h | 1 +
block/block-backend.c | 19 +++++++++++++------
qemu-img.c | 2 +-
3 files changed, 15 insertions(+), 7 deletions(-)
--
2.30.2
next reply other threads:[~2021-04-22 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 16:43 Kevin Wolf [this message]
2021-04-22 16:43 ` [PATCH v2 1/2] block: Add BDRV_O_NO_SHARE for blk_new_open() Kevin Wolf
2021-04-22 18:41 ` Eric Blake
2021-04-23 9:43 ` Vladimir Sementsov-Ogievskiy
2021-04-23 13:58 ` Kevin Wolf
2021-04-22 16:43 ` [PATCH v2 2/2] qemu-img convert: Unshare write permission for source Kevin Wolf
2021-04-23 15:17 ` Vladimir Sementsov-Ogievskiy
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=20210422164344.283389-1-kwolf@redhat.com \
--to=kwolf@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).