diff options
| author | Max Reitz <mreitz@redhat.com> | 2019-05-22 19:03:48 +0200 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2019-06-18 16:41:10 +0200 |
| commit | a193ad3b3b27eec6914bd3cd7dc4bff02f59177f (patch) | |
| tree | 0e82e6beac2c04437909d49513769556253ad0b8 /block | |
| parent | f94dc3b414028bc762f51ea66c170276130d5f8a (diff) | |
block/commit: Drop bdrv_child_try_set_perm()
commit_top_bs never requests or unshares any permissions. There is no
reason to make this so explicit here.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'block')
| -rw-r--r-- | block/commit.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/block/commit.c b/block/commit.c index c815def89a..212c6f639e 100644 --- a/block/commit.c +++ b/block/commit.c @@ -110,8 +110,6 @@ static void commit_abort(Job *job) * XXX Can (or should) we somehow keep 'consistent read' blocked even * after the failed/cancelled commit job is gone? If we already wrote * something to base, the intermediate images aren't valid any more. */ - bdrv_child_try_set_perm(s->commit_top_bs->backing, 0, BLK_PERM_ALL, - &error_abort); bdrv_replace_node(s->commit_top_bs, backing_bs(s->commit_top_bs), &error_abort); |