Skip to content

improve qom debugging and fix a dangling MemoryRegion in rutabaga

Roman Kiryanov qemu-devel 2 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest2 patches 1 replyIn review
  2. v12 patches 2 repliesSuperseded

Changes in v2 from the cover letter

- Updated clearing of obj->properties using g_clear_pointer.
- Moved clearing of obj->class into object_deinit.
- obj->class is checked to be NULL before obj->free(obj).

Patches in v2 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2qom: improve use-after-free debuggingqom/object.c+5 -11 reply
2/2display: rutabaga: unparent MemoryRegions in unmaphw/display/virtio-gpu-rutabaga.c+1 -00 replies

Reviews trailers per patch

1 of 2 patches has a Reviewed-by or Acked-by.

PatchPhilippe Mathieu-Daudé
1/2R-b
2/2

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v2 thread

Cover letter [PATCH v2 0/2] improve qom debugging and fix a dangling MemoryRegion in rutabaga

Hi, this series of patches fixes a dangling MemoryRegion in rutabaga and also brings the debugging changes I used to locate it.

Changes in v2:
- Updated clearing of obj->properties using g_clear_pointer.
- Moved clearing of obj->class into object_deinit.
- obj->class is checked to be NULL before obj->free(obj).

Roman Kiryanov (2):
qom: improve use-after-free debugging
display: rutabaga: unparent MemoryRegions in unmap

 hw/display/virtio-gpu-rutabaga.c | 1 +
 qom/object.c                     | 6 +++++-
 2 files changed, 6 insertions(+), 1 deletion(-)
Signature · 1 line
2.54.0.545.g6539524ca2-goog