block: Use bdrv_default_perms()
bdrv_default_perms() can decide which permission profile to use based on the BdrvChildRole, so block drivers do not need to select it explicitly. The blkverify driver now no longer shares the WRITE permission for the image to verify. We thus have to adjust two places in test-block-iothread not to take it. (Note that in theory, blkverify should behave like quorum in this regard and share neither WRITE nor RESIZE for both of its children. In practice, it does not really matter, because blkverify is used only for debugging, so we might as well keep its permissions rather liberal.) Signed-off-by:Max Reitz <mreitz@redhat.com> Reviewed-by:
Eric Blake <eblake@redhat.com> Message-Id: <20200513110544.176672-30-mreitz@redhat.com> Signed-off-by:
Kevin Wolf <kwolf@redhat.com>
Showing
- block/backup-top.c 2 additions, 2 deletionsblock/backup-top.c
- block/blkdebug.c 2 additions, 2 deletionsblock/blkdebug.c
- block/blklogwrites.c 2 additions, 7 deletionsblock/blklogwrites.c
- block/blkreplay.c 1 addition, 1 deletionblock/blkreplay.c
- block/blkverify.c 1 addition, 1 deletionblock/blkverify.c
- block/bochs.c 1 addition, 1 deletionblock/bochs.c
- block/cloop.c 1 addition, 1 deletionblock/cloop.c
- block/crypto.c 1 addition, 1 deletionblock/crypto.c
- block/dmg.c 1 addition, 1 deletionblock/dmg.c
- block/filter-compress.c 1 addition, 1 deletionblock/filter-compress.c
- block/parallels.c 1 addition, 1 deletionblock/parallels.c
- block/qcow.c 1 addition, 1 deletionblock/qcow.c
- block/qcow2.c 1 addition, 1 deletionblock/qcow2.c
- block/qed.c 1 addition, 1 deletionblock/qed.c
- block/raw-format.c 1 addition, 1 deletionblock/raw-format.c
- block/throttle.c 1 addition, 1 deletionblock/throttle.c
- block/vdi.c 1 addition, 1 deletionblock/vdi.c
- block/vhdx.c 1 addition, 1 deletionblock/vhdx.c
- block/vmdk.c 1 addition, 1 deletionblock/vmdk.c
- block/vpc.c 1 addition, 1 deletionblock/vpc.c
Loading
Please register or sign in to comment