From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Fam Zheng <famz@redhat.com>
Subject: [Qemu-devel] [PATCH 2/9] block: BLK_PERM_WRITE includes ..._UNCHANGED
Date: Mon, 16 Apr 2018 18:58:42 +0200 [thread overview]
Message-ID: <20180416165849.28864-3-mreitz@redhat.com> (raw)
In-Reply-To: <20180416165849.28864-1-mreitz@redhat.com>
Currently we never actually check whether the WRITE_UNCHANGED
permission has been taken for unchanging writes. But the one check that
is commented out checks both WRITE and WRITE_UNCHANGED; and considering
that WRITE_UNCHANGED is already documented as being weaker then WRITE,
we should probably explicitly document WRITE to include WRITE_UNCHANGED.
Signed-off-by: Max Reitz <mreitz@redhat.com>
---
include/block/block.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/block/block.h b/include/block/block.h
index cdec3639a3..397b5e8d44 100644
--- a/include/block/block.h
+++ b/include/block/block.h
@@ -205,6 +205,9 @@ enum {
* This permission (which is weaker than BLK_PERM_WRITE) is both enough and
* required for writes to the block node when the caller promises that
* the visible disk content doesn't change.
+ *
+ * As the BLK_PERM_WRITE permission is strictly stronger, either is
+ * sufficient to perform an unchanging write.
*/
BLK_PERM_WRITE_UNCHANGED = 0x04,
--
2.14.3
next prev parent reply other threads:[~2018-04-16 16:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 16:58 [Qemu-devel] [PATCH 0/9] block: Add COR filter driver Max Reitz
2018-04-16 16:58 ` [Qemu-devel] [PATCH 1/9] " Max Reitz
2018-04-20 8:31 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-04-20 13:21 ` Max Reitz
2018-04-16 16:58 ` Max Reitz [this message]
2018-04-20 8:32 ` [Qemu-devel] [Qemu-block] [PATCH 2/9] block: BLK_PERM_WRITE includes ..._UNCHANGED Stefan Hajnoczi
2018-04-20 12:04 ` Alberto Garcia
2018-04-20 13:22 ` Max Reitz
2018-04-16 16:58 ` [Qemu-devel] [PATCH 3/9] block: Add BDRV_REQ_WRITE_UNCHANGED flag Max Reitz
2018-04-20 8:33 ` Stefan Hajnoczi
2018-04-20 12:06 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2018-04-16 16:58 ` [Qemu-devel] [PATCH 4/9] block: Set BDRV_REQ_WRITE_UNCHANGED for COR writes Max Reitz
2018-04-20 8:33 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-04-20 12:06 ` Alberto Garcia
2018-04-16 16:58 ` [Qemu-devel] [PATCH 5/9] block/quorum: Support BDRV_REQ_WRITE_UNCHANGED Max Reitz
2018-04-20 8:44 ` Stefan Hajnoczi
2018-04-20 12:09 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2018-04-16 16:58 ` [Qemu-devel] [PATCH 6/9] block: Support BDRV_REQ_WRITE_UNCHANGED in filters Max Reitz
2018-04-20 8:35 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-04-20 12:19 ` Alberto Garcia
2018-04-16 16:58 ` [Qemu-devel] [PATCH 7/9] iotests: Clean up wrap image in 197 Max Reitz
2018-04-20 8:38 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-04-20 12:20 ` Alberto Garcia
2018-04-16 16:58 ` [Qemu-devel] [PATCH 8/9] iotests: Copy 197 for COR filter driver Max Reitz
2018-04-20 8:38 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-04-16 16:58 ` [Qemu-devel] [PATCH 9/9] iotests: Add test for COR across nodes Max Reitz
2018-04-20 8:43 ` Stefan Hajnoczi
2018-04-20 13:22 ` Max Reitz
2018-04-20 7:49 ` [Qemu-devel] [PATCH 0/9] block: Add COR filter driver Stefan Hajnoczi
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=20180416165849.28864-3-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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;
as well as URLs for NNTP newsgroup(s).