From: Maxim Levitsky <mlevitsk@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: [PATCH 0/2] Fix for write sharing on luks raw images
Date: Sun, 19 Jul 2020 15:20:57 +0300 [thread overview]
Message-ID: <20200719122059.59843-1-mlevitsk@redhat.com> (raw)
A rebase gone wrong, and I ended up allowing a luks image
to be opened at the same time by two VMs without any warnings/overrides.
Fix that and also add an iotest to prevent this from happening.
Best regards,
Maxim Levisky
Maxim Levitsky (2):
block/crypto: disallow write sharing by default
qemu-iotests: add testcase for bz #1857490
block/crypto.c | 2 +-
tests/qemu-iotests/296 | 44 +++++++++++++++++++++++++++++++++++++-
tests/qemu-iotests/296.out | 12 +++++++++--
3 files changed, 54 insertions(+), 4 deletions(-)
--
2.26.2
next reply other threads:[~2020-07-19 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 12:20 Maxim Levitsky [this message]
2020-07-19 12:20 ` [PATCH 1/2] block/crypto: disallow write sharing by default Maxim Levitsky
2020-07-19 12:20 ` [PATCH 2/2] qemu-iotests: add testcase for bz #1857490 Maxim Levitsky
2020-07-19 12:28 ` [PATCH 0/2] Fix for write sharing on luks raw images no-reply
2020-07-20 12:37 ` Max Reitz
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=20200719122059.59843-1-mlevitsk@redhat.com \
--to=mlevitsk@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).