Markus Armbruster <arm...@redhat.com> writes: > Recent commit 6952026120 "monitor: Tidy up find_device_state()" > assumed the function's argument is "the device's ID or QOM path" (as > documented for device_del). It's actually either an absolute QOM > path, or a QOM path relative to /machine/peripheral/. Such a relative > path is a device ID when it doesn't contain a slash. When it does, > the function now always fails. Broke iotest 200, which uses relative > path "vda/virtio-backend". > > It fails because object_resolve_path_component() resolves just one > component, not a relative path. > > The obvious function to resolve relative paths is > object_resolve_path(). It picks a parent automatically. Too much > magic, we want to specify the parent. Create new > object_resolve_path_at() for that, and use it in find_device_state(). > > Reported-by: Christian Borntraeger <borntrae...@de.ibm.com> > Signed-off-by: Markus Armbruster <arm...@redhat.com>
Queued for 6.2 & PR sent.
