[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [qemu-s390x] [Qemu-devel] [PATCH] call HotplugHandler->plug() as the
Re: [qemu-s390x] [Qemu-devel] [PATCH] call HotplugHandler->plug() as the last step in device realization
Tue, 30 Oct 2018 16:15:52 +0100
On Wed, 24 Oct 2018 15:09:36 +0200
David Hildenbrand <address@hidden> wrote:
> On 16.10.18 15:56, Igor Mammedov wrote:
> > On Tue, 16 Oct 2018 15:33:40 +0200
> > Igor Mammedov <address@hidden> wrote:
> >> When  was fixed it was agreed that adding and calling post_plug()
> >> callback after device_reset() was low risk approach to hotfix issue
> >> right before release. So it was merged instead of moving already
> >> existing plug() callback after device_reset() is called which would
> >> be more risky and require all plug() callbacks audit.
> >> Looking at the current plug() callbacks, it doesn't seem that moving
> >> plug() callback after device_reset() is breaking anything, so here
> >> goes agreed upon  proper fix which essentially reverts 
> >> and moves plug() callback after device_reset().
> >> This way devices always comes to plug() stage, after it's been fully
> >> initialized (including being reset), which fixes race condition 
> >> without need for an extra post_plug() callback.
> >> 1. (25e897881 "qdev: add HotplugHandler->post_plug() callback")
> >> 2. (8449bcf94 "virtio-scsi: fix hotplug ->reset() vs event race")
> >> 3. https://www.mail-archive.com/address@hidden/msg549915.html
> >> Signed-off-by: Igor Mammedov <address@hidden>
> >> ---
> >> TODO:
> >> remove usage of Error** from plug() callback, we need to factor out
> >> pre_plug part from plug() callbacks, before proceeding with it.
> >> DavidH has recently finished it for pc-dimm/memory_devices, cpus
> >> mostly have pre_plug parts factored out, but there still are parts
> >> that could fail so it needs some more work to eliminate failure points
> >> from plug() callbacks. Meanwhile, I'll plan to treat other misc
> >> handlers (pci[e]/acpi/usb/...) and introduce pre_plug() where
> >> necessary.
> Saw this mail just now. I guess we should do more. Especially what seems
> to be fragile is errors during unrealize() and unplug().
> Errors during unplug() should only ever happen if it was not triggered
> via unplug_request(). Otherwise, unplug_request() should check for all
> possible errors and unplug() will not result in errors.
Not sure that I read it right, I see 2 cases:
1: unplug_request == NULL (i.e. where surprise device removal is supported)
should not fail
2: unplug_request != NULL && unplug() is called by guest side, it's caller
policy to decide what to do on failure. One use case is NOP, i.e. caller
should not destroy object if unplug() fails and unplug() should fail without
side effects, and possibly notify guest about it if such mechanism is
Could be tricky to handle errors in case of chained handlers.
> Also, errors during unrealize() should definitely be avoided. Or even
> forbidden. E.g. looking at hw/core/qdev.c:device_set_realized,
> 1. failing to unrealize might already have resulted in the unplug
> handler getting called.
> 2. will result in a unparent of the device and therefore removal
> 3. will have already eventually unrealized child devices or buses.
> To summarize, failing in unrealize() is a bad idea and might leave the
> rest of the system in a very unpredictable state.
failure path isn't really usable here, I'd assume that initial idea
was that unrealize() could fail cleanly and let caller to decide on
what to do. But with child bus handling and co it won't really work.
BTW what devices are the users of DeviceState::child_bus,
I don't think that we have any composite devices that actually
exercise realize() part of it and maybe unrealize() part.