From: Arun Menon <armenon@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Peter Xu" <peterx@redhat.com>, "Fabiano Rosas" <farosas@suse.de>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Arun Menon" <armenon@redhat.com>
Subject: [PATCH v3 0/2] migration/vmstate: Add VMState support to safely migrate GByteArray
Date: Wed, 22 Apr 2026 13:52:12 +0530 [thread overview]
Message-ID: <20260422082214.10390-1-armenon@redhat.com> (raw)
In GLib, GByteArray is an object managed by the library. Currently,
migrating a GByteArray requires treating it as a raw C struct and using
VMSTATE_VBUFFER_ALLOC_UINT32. For example, see vmstate_vdba in
ui/vdagent.c
QEMU cannot pretend that GByteArray is a C struct and simply use
VMS_ALLOC to g_malloc() the buffer. This is because, VMS_ALLOC blindly
overwrites the data pointer with a newly allocated buffer, thereby
leaking the previous memory. Besides, GLib tracks the array's capacity
in a hidden alloc field. Bypassing GLib APIs leave this capacity out of
sync with the newly allocated buffer, potentially leading to heap buffer
overflows during subsequent g_byte_array_append() calls.
This series adds a new VMState called VMSTATE_GBYTEARRAY, which will
directly use GLib library API calls to create, or resize the object.
This is then used in ui/vdaagent.c replacing the use of
VMSTATE_VBUFFER_ALLOC_UINT32.
Changes in v3:
- Add assert() checks to get and put functions to prevent NULL pointer
dereferences, as suggested by Peter Xu.
Changes in v2:
- Marc-André pointed out the problem of not updating the device state
itself. To do that we should essentially pass a pointer to the
GByteArray pointer. Remove VMS_POINTER from VMSTATE_GBYTEARRAY. This
changes 'pv' to be the address of the pointer field (GByteArray **)
instead of the pointer's value.
- Update get_g_byte_array and put_g_byte_array to handle this additional
level of indirection, allowing safe allocation and updating device state.
- Link to v1: https://lore.kernel.org/all/20260406115247.4879-1-armenon@redhat.com/
Arun Menon (2):
migration/vmstate: Add VMState support for GByteArray
ui/vdagent: Use VMSTATE_GBYTEARRAY to safely migrate outbuf
include/migration/vmstate.h | 10 ++++++++++
migration/vmstate-types.c | 37 +++++++++++++++++++++++++++++++++++++
ui/vdagent.c | 13 +------------
3 files changed, 48 insertions(+), 12 deletions(-)
--
2.53.0
next reply other threads:[~2026-04-22 8:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 8:22 Arun Menon [this message]
2026-04-22 8:22 ` [PATCH v3 1/2] migration/vmstate: Add VMState support for GByteArray Arun Menon
2026-04-22 19:58 ` Peter Xu
2026-04-23 7:28 ` Arun Menon
2026-04-23 15:34 ` Peter Xu
2026-04-22 8:22 ` [PATCH v3 2/2] ui/vdagent: Use VMSTATE_GBYTEARRAY to safely migrate outbuf Arun Menon
2026-04-22 19:59 ` Peter Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260422082214.10390-1-armenon@redhat.com \
--to=armenon@redhat.com \
--cc=farosas@suse.de \
--cc=marcandre.lureau@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.