block: consistently use bdrv_is_read_only()
It's better to use accessor function instead of bs->read_only directly. In some places use bdrv_is_writable() instead of checking both BDRV_O_RDWR set and BDRV_O_INACTIVE not set. In bdrv_open_common() it's a bit strange to add one more variable, but we are going to drop bs->read_only in the next patch, so new ro local variable substitutes it here. Signed-off-by:Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> Message-Id: <20210527154056.70294-2-vsementsov@virtuozzo.com> Signed-off-by:
Kevin Wolf <kwolf@redhat.com>
Showing
- block.c 7 additions, 4 deletionsblock.c
- block/block-backend.c 1 addition, 1 deletionblock/block-backend.c
- block/commit.c 1 addition, 1 deletionblock/commit.c
- block/io.c 2 additions, 2 deletionsblock/io.c
- block/qapi.c 1 addition, 1 deletionblock/qapi.c
- block/qcow2-snapshot.c 1 addition, 1 deletionblock/qcow2-snapshot.c
- block/qcow2.c 2 additions, 3 deletionsblock/qcow2.c
- block/snapshot.c 1 addition, 1 deletionblock/snapshot.c
- block/vhdx-log.c 1 addition, 1 deletionblock/vhdx-log.c
Loading
Please register or sign in to comment