summaryrefslogtreecommitdiff
path: root/gitdm.config
diff options
context:
space:
mode:
authorMax Reitz <mreitz@redhat.com>2019-06-11 21:19:26 +0200
committerKevin Wolf <kwolf@redhat.com>2020-09-07 12:31:31 +0200
commit05ea385afdfe5d0886265880bfd14d17192beb03 (patch)
treec4fa1cb6bf4cdf5be2e4349c139b46791e3a7ab1 /gitdm.config
parentf1a7f18f07ef41b4d078621bd6e515165106d91f (diff)
downloadqemu-05ea385afdfe5d0886265880bfd14d17192beb03.zip
blockdev: Fix active commit choice
We have to perform an active commit whenever the top node has a parent that has taken the WRITE permission on it. This means that block-commit's @backing-file parameter is no longer allowed for such nodes, and that users will have to issue a block-job-complete command. Neither should pose a problem in practice, because this case was basically just broken until now. (Since this commit already touches block-commit's documentation, it also moves up the chunk explaining general block-commit behavior that for some reason was situated under @backing-file.) Signed-off-by: Max Reitz <mreitz@redhat.com>
Diffstat (limited to 'gitdm.config')
0 files changed, 0 insertions, 0 deletions