Repository navigation
Conversation
A vfio-user DMA unmap on virtio-mem unplug writes to the client socket with send(2), which the virtio-mem seccomp filter refused, so the VMM died with SIGSYS when a guest with a vfio-user device shrank its memory. Signed-off-by: Alex Zenla <alex@edera.dev>
bleggett
approved these changes
Nov 17, 2026
alexandermerritt
approved these changes
Nov 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A guest with a vfio-user device and a virtio-mem memory zone kills the VMM with SIGSYS when it gives memory back:
On unplug, the virtio-mem thread asks the vfio-user client to unmap the range.
vfio_user::Client::dma_unmapsends the request withwrite_all, which issend(2), and the virtio-mem seccomp filter only allowssendmsgandrecvfrom. DMA map is not affected because it passes an fd and usessendmsg.This adds
sendtoto the virtio-mem thread rules.Tested with a guest on a virtio-mem zone (
--memory size=0,hotplug_method=virtio-mem --memory-zone id=memz0,size=512M,shared=on,hotplug_size=1G) and a vfio-user device (--user-device), resizing the zone up and down withch-remote resize-zone: before the change the VMM dies on the shrink, after it the VMM keeps running and shuts down cleanly. Also tested with an Edera KVM zone that runs its disks on a vfio-user NVMe device.