summaryrefslogtreecommitdiff
path: root/hw/microblaze/petalogix_s3adsp1800_mmu.c
diff options
context:
space:
mode:
authorKevin Wolf <kwolf@redhat.com>2021-04-22 18:43:44 +0200
committerKevin Wolf <kwolf@redhat.com>2021-04-30 12:27:48 +0200
commit0b8fb55ce6398d7277b5ba0f19e39ec30a058191 (patch)
tree72da2e3cf332be379b01e4aa72d4582b3c4737c0 /hw/microblaze/petalogix_s3adsp1800_mmu.c
parent35b7f4abd5afe159f91ddeb4f2a40c20d2f48367 (diff)
downloadqemu-0b8fb55ce6398d7277b5ba0f19e39ec30a058191.zip
qemu-img convert: Unshare write permission for source
For a successful conversion of an image, we must make sure that its content doesn't change during the conversion. A special case of this is using the same image file both as the source and as the destination. If both input and output format are raw, the operation would just be useless work, with other formats it is a sure way to destroy the image. This will now fail because the image file can't be opened a second time for the output when opening it for the input has already acquired file locks to unshare BLK_PERM_WRITE. Nevertheless, if there is some reason in a special case why it is actually okay to allow writes to the image while it is being converted, -U can still be used to force sharing all permissions. Note that for most image formats, BLK_PERM_WRITE would already be unshared by the format driver, so this only really makes a difference for raw source images (but any output format). Reported-by: Xueqiang Wei <xuwei@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Message-Id: <20210422164344.283389-3-kwolf@redhat.com> Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'hw/microblaze/petalogix_s3adsp1800_mmu.c')
0 files changed, 0 insertions, 0 deletions