Visitar URL original
docs(changelog): note the virtio-mem block state fix · firecracker-microvm/firecracker@39eca9d · GitHub
Skip to content

Commit 39eca9d

Browse files
not4snot4s
committed
docs(changelog): note the virtio-mem block state fix
Record that virtio-mem now commits a slot's block state only after its KVM update succeeds, keeping the device's bookkeeping consistent with KVM when a plug or unplug request fails part way through. Signed-off-by: Jay Chung <jaehoc@amazon.com>
1 parent b742132 commit 39eca9d

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -88,6 +88,12 @@ and this project adheres to
8888
`virtio-mem` discarding the whole hotpluggable region on every `UNPLUG_ALL`
8989
request, even when nothing was plugged. The discard is now skipped when the
9090
range has no plugged blocks.
91+
- [#6176](https://github.com/firecracker-microvm/firecracker/pull/6176): Fixed
92+
`virtio-mem` leaving its block accounting inconsistent with the KVM memory
93+
slots if a plug or unplug request failed part way through. Firecracker now
94+
commits each slot's state only after its KVM update succeeds, so a partial
95+
failure leaves the block state and the KVM slots reflecting exactly the slots
96+
that were updated.
9197
- [#5956](https://github.com/firecracker-microvm/firecracker/pull/5956): Fixed a
9298
TOCTOU race in the aarch64 jailer when setting ownership of the CPU cache and
9399
`MIDR_EL1` information files copied into the chroot.

0 commit comments

Comments
 (0)