Blame SOURCES/kvm-block-BLK_PERM_WRITE-includes-._UNCHANGED.patch

383d26
From 68b3e533a4531486fe346f042e190fb5c426f24f Mon Sep 17 00:00:00 2001
383d26
From: Max Reitz <mreitz@redhat.com>
383d26
Date: Mon, 18 Jun 2018 16:12:05 +0200
383d26
Subject: [PATCH 29/54] block: BLK_PERM_WRITE includes ..._UNCHANGED
383d26
383d26
RH-Author: Max Reitz <mreitz@redhat.com>
383d26
Message-id: <20180618161212.14444-4-mreitz@redhat.com>
383d26
Patchwork-id: 80763
383d26
O-Subject: [RHV-7.6 qemu-kvm-rhev PATCH 03/10] block: BLK_PERM_WRITE includes ..._UNCHANGED
383d26
Bugzilla: 1518738
383d26
RH-Acked-by: John Snow <jsnow@redhat.com>
383d26
RH-Acked-by: Kevin Wolf <kwolf@redhat.com>
383d26
RH-Acked-by: Miroslav Rezanina <mrezanin@redhat.com>
383d26
383d26
Currently we never actually check whether the WRITE_UNCHANGED
383d26
permission has been taken for unchanging writes.  But the one check that
383d26
is commented out checks both WRITE and WRITE_UNCHANGED; and considering
383d26
that WRITE_UNCHANGED is already documented as being weaker than WRITE,
383d26
we should probably explicitly document WRITE to include WRITE_UNCHANGED.
383d26
383d26
Signed-off-by: Max Reitz <mreitz@redhat.com>
383d26
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
383d26
Reviewed-by: Alberto Garcia <berto@igalia.com>
383d26
Message-id: 20180421132929.21610-3-mreitz@redhat.com
383d26
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
383d26
Signed-off-by: Max Reitz <mreitz@redhat.com>
383d26
(cherry picked from commit 24b7c538fea86b598e2a335f4805a0ab50a30e98)
383d26
Signed-off-by: Max Reitz <mreitz@redhat.com>
383d26
Signed-off-by: Miroslav Rezanina <mrezanin@redhat.com>
383d26
---
383d26
 include/block/block.h | 3 +++
383d26
 1 file changed, 3 insertions(+)
383d26
383d26
diff --git a/include/block/block.h b/include/block/block.h
383d26
index cdec363..397b5e8 100644
383d26
--- a/include/block/block.h
383d26
+++ b/include/block/block.h
383d26
@@ -205,6 +205,9 @@ enum {
383d26
      * This permission (which is weaker than BLK_PERM_WRITE) is both enough and
383d26
      * required for writes to the block node when the caller promises that
383d26
      * the visible disk content doesn't change.
383d26
+     *
383d26
+     * As the BLK_PERM_WRITE permission is strictly stronger, either is
383d26
+     * sufficient to perform an unchanging write.
383d26
      */
383d26
     BLK_PERM_WRITE_UNCHANGED    = 0x04,
383d26
 
383d26
-- 
383d26
1.8.3.1
383d26