[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-block] [PATCH 12/54] block: Add op blocker permission constant
From: |
Fam Zheng |
Subject: |
Re: [Qemu-block] [PATCH 12/54] block: Add op blocker permission constants |
Date: |
Thu, 23 Feb 2017 19:53:12 +0800 |
User-agent: |
Mutt/1.7.1 (2016-10-04) |
On Tue, 02/21 15:58, Kevin Wolf wrote:
> This patch defines the permission categories that will be used by the
> new op blocker system.
>
> Signed-off-by: Kevin Wolf <address@hidden>
> ---
> include/block/block.h | 35 +++++++++++++++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
>
> diff --git a/include/block/block.h b/include/block/block.h
> index bde5ebd..ac40c8d 100644
> --- a/include/block/block.h
> +++ b/include/block/block.h
> @@ -187,6 +187,41 @@ typedef enum BlockOpType {
> BLOCK_OP_TYPE_MAX,
> } BlockOpType;
>
> +/* Block node permission constants */
> +enum {
> + /**
> + * A user that has the "permission" of consistent reads is guaranteed
> that
> + * their view of the contents of the block device is complete and
> + * self-consistent, repesenting the contents of a disk at a specific
> point.
*representing
> + *
> + * For most block devices (including their backing files) this is true,
> but
> + * the property cannot be maintained in a few situations like for
> + * intermediate nodes of a commit block job.
> + */
> + BLK_PERM_CONSISTENT_READ = 0x01,
> +
> + /** This permission is required to change the visible disk contents. */
> + BLK_PERM_WRITE = 0x02,
> +
> + /**
> + * 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
> + * this visible disk contents doesn't change.
"contents doesn't" sounds weird to me, but I'm not very sure.
> + */
> + BLK_PERM_WRITE_UNCHANGED = 0x04,
> +
> + /** This permission is required to change the size of a block node. */
> + BLK_PERM_RESIZE = 0x08,
> +
> + /**
> + * This permission is required to change the node that this BdrvChild
> + * points to.
> + */
> + BLK_PERM_GRAPH_MOD = 0x10,
> +
> + BLK_PERM_ALL = 0x1f,
> +};
> +
> /* disk I/O throttling */
> void bdrv_init(void);
> void bdrv_init_with_whitelist(void);
> --
> 1.8.3.1
>
Fam
- Re: [Qemu-block] [PATCH 08/54] block: Factor out bdrv_open_driver(), (continued)
- [Qemu-block] [PATCH 12/54] block: Add op blocker permission constants, Kevin Wolf, 2017/02/21
- [Qemu-block] [PATCH 14/54] block: Let callers request permissions when attaching a child node, Kevin Wolf, 2017/02/21
- [Qemu-block] [PATCH 11/54] tests: Use opened block node for block job tests, Kevin Wolf, 2017/02/21
- [Qemu-block] [PATCH 13/54] block: Add Error argument to bdrv_attach_child(), Kevin Wolf, 2017/02/21
- [Qemu-block] [PATCH 15/54] block: Involve block drivers in permission granting, Kevin Wolf, 2017/02/21