block/vhdx: fix dynamic VHDX BAT corruption
commit8af037fe4cfeb88bbcded3122cec2c5be0b90907
authorLukas Tschoke <lukts330@gmail.com>
Fri, 7 Apr 2023 22:11:38 +0000 (8 00:11 +0200)
committerKevin Wolf <kwolf@redhat.com>
Tue, 11 Apr 2023 11:53:03 +0000 (11 13:53 +0200)
treec88b5196ac5eb2ade7784a54d45684b71c1de65a
parentdda860b9c031d6a2768f75e5e622545d41d4b688
block/vhdx: fix dynamic VHDX BAT corruption

The corruption occurs when a BAT entry aligned to 4096 bytes is changed.

Specifically, the corruption occurs during the creation of the LOG Data
Descriptor. The incorrect behavior involves copying 4088 bytes from the
original 4096 bytes aligned offset to `tmp[8..4096]` and then copying
the new value for the first BAT entry to the beginning `tmp[0..8]`.
This results in all existing BAT entries inside the 4K region being
incorrectly moved by 8 bytes and the last entry being lost.

This bug did not cause noticeable corruption when only sequentially
writing once to an empty dynamic VHDX (e.g.
using `qemu-img convert -O vhdx -o subformat=dynamic ...`), but it
still resulted in invalid values for the (unused) Sector Bitmap BAT
entries.

Importantly, this corruption would only become noticeable after the
corrupted BAT is re-read from the file.

Resolves: https://gitlab.com/qemu-project/qemu/-/issues/727
Cc: qemu-stable@nongnu.org
Signed-off-by: Lukas Tschoke <lukts330@gmail.com>
Message-Id: <6cfb6d6b-adc5-7772-c8a5-6bae9a0ad668@gmail.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
block/vhdx-log.c