From: Fam Zheng <famz@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-devel@nongnu.org, "Daniel P. Berrange" <berrange@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, rjones@redhat.com
Subject: Re: [Qemu-devel] [PATCH 14/14] tests: Add test-image-lock
Date: Fri, 9 Dec 2016 15:39:20 +0800 [thread overview]
Message-ID: <20161209073920.GA562@lemon> (raw)
In-Reply-To: <f89973af-5db3-a85d-0539-0a8ec0079fd6@redhat.com>
On Fri, 12/02 17:30, Max Reitz wrote:
> > +static struct CompatData {
> > + bool write_1;
> > + bool share_1;
> > + bool write_2;
> > + bool share_2;
> > + bool compatible;
> > +} compat_data[] = {
> > + /* Write 1, Share 1, Write 2, Share 2, Compatible. */
> > + { RO, SHARE, RO, SHARE, true, },
> > + { RO, SHARE, RO, EXCLU, true, },
> > + { RO, SHARE, RW, SHARE, true, },
> > + { RO, SHARE, RW, EXCLU, true, },
> > + { RO, EXCLU, RO, SHARE, true, },
> > + { RO, EXCLU, RO, EXCLU, true, },
> > + { RO, EXCLU, RW, SHARE, false, },
> > + { RO, EXCLU, RW, EXCLU, false, },
> > +};
>
> Without having looked closer at the test, what about RW/RW compatibility?
Good catch, I will fix this matrix in next version.
Fam
next prev parent reply other threads:[~2016-12-09 7:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 15:38 [Qemu-devel] [PATCH 00/14] block: Image locking series Fam Zheng
2016-10-31 15:38 ` [Qemu-devel] [PATCH 01/14] osdep: Add qemu_lock_fd and qemu_unlock_fd Fam Zheng
2016-12-02 0:30 ` Max Reitz
2016-12-08 6:53 ` Fam Zheng
2016-10-31 15:38 ` [Qemu-devel] [PATCH 02/14] block: Define BDRV_O_SHARE_RW Fam Zheng
2016-10-31 15:38 ` [Qemu-devel] [PATCH 03/14] qemu-io: Set "share-rw" flag together with read-only Fam Zheng
2016-10-31 15:38 ` [Qemu-devel] [PATCH 04/14] qemu-img: Set "share-rw" flag in read-only commands Fam Zheng
2016-12-02 0:52 ` Max Reitz
2016-12-08 7:19 ` Fam Zheng
2016-10-31 15:38 ` [Qemu-devel] [PATCH 05/14] block: Set "share-rw" flag in drive-backup when sync=none Fam Zheng
2016-12-02 1:01 ` Max Reitz
2016-10-31 15:38 ` [Qemu-devel] [PATCH 06/14] block: Set "share-rw" flag for incoming migration Fam Zheng
2016-12-02 1:22 ` Max Reitz
2016-10-31 15:38 ` [Qemu-devel] [PATCH 07/14] iotests: 055: Don't attach the drive to vm for drive-backup Fam Zheng
2016-10-31 15:38 ` [Qemu-devel] [PATCH 08/14] iotests: 030: Read-only open image for getting map Fam Zheng
2016-10-31 15:38 ` [Qemu-devel] [PATCH 09/14] iotests: 087: Don't attch test image twice Fam Zheng
2016-10-31 15:38 ` [Qemu-devel] [PATCH 10/14] iotests: 085: Avoid image locking conflict Fam Zheng
2016-10-31 15:38 ` [Qemu-devel] [PATCH 11/14] iotests: 091: Quit QEMU before checking image Fam Zheng
2016-10-31 15:38 ` [Qemu-devel] [PATCH 12/14] tests: Use null-co:// instead of /dev/null as the dummy image Fam Zheng
2016-10-31 15:38 ` [Qemu-devel] [PATCH 13/14] raw-posix: Implement image locking Fam Zheng
2016-10-31 22:01 ` Eric Blake
2016-10-31 22:39 ` Richard W.M. Jones
2016-11-01 2:06 ` Fam Zheng
2016-12-02 2:58 ` Max Reitz
2017-01-18 10:48 ` Fam Zheng
2017-01-18 13:02 ` Max Reitz
2017-01-18 13:19 ` Fam Zheng
2016-12-02 16:13 ` Max Reitz
2016-10-31 15:38 ` [Qemu-devel] [PATCH 14/14] tests: Add test-image-lock Fam Zheng
2016-12-02 16:30 ` Max Reitz
2016-12-09 7:39 ` Fam Zheng [this message]
2016-12-02 3:10 ` [Qemu-devel] [PATCH 00/14] block: Image locking series 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=20161209073920.GA562@lemon \
--to=famz@redhat.com \
--cc=berrange@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
/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