diff options
| author | Benjamin Berg <[email protected]> | 2024-11-03 22:28:51 +0100 |
|---|---|---|
| committer | Johannes Berg <[email protected]> | 2024-11-07 17:39:57 +0100 |
| commit | fcbd26d33dfa40496b6d82973bc49f95e6df21f9 (patch) | |
| tree | c3c4d5a06e1f6b0683e5e596404f3d646b1ffcef | |
| parent | ce6e85a186c28ab0ca024580cba93fa19147c72b (diff) | |
um: virtio_uml: send SET_MEM_TABLE message with the exact size
The rust based userspace vhost devices are very strict and will not
accept the message if it is longer than required. So, only include the
data for the first memory region.
Signed-off-by: Benjamin Berg <[email protected]>
Link: https://patch.msgid.link/[email protected]
Signed-off-by: Johannes Berg <[email protected]>
| -rw-r--r-- | arch/um/drivers/virtio_uml.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/um/drivers/virtio_uml.c b/arch/um/drivers/virtio_uml.c index 4d3e9b9f5b61..c602892f329f 100644 --- a/arch/um/drivers/virtio_uml.c +++ b/arch/um/drivers/virtio_uml.c @@ -623,7 +623,7 @@ static int vhost_user_set_mem_table(struct virtio_uml_device *vu_dev) { struct vhost_user_msg msg = { .header.request = VHOST_USER_SET_MEM_TABLE, - .header.size = sizeof(msg.payload.mem_regions), + .header.size = offsetof(typeof(msg.payload.mem_regions), regions[1]), .payload.mem_regions.num = 1, }; unsigned long reserved = uml_reserved - uml_physmem; |