Martin Pitt
f3f8a96a82
The QMP client's userdata (the `VmspawnQmpBridge`, vmspawn's QPM state) and its event callback were previously only set up in `vmspawn_varlink_setup()`, after the VM has been resumed. This caused two problems: - Boot-time device setup could not wait for its own completion before the VM is resumed, as that needs exactly these replies and events. - QMP replies and events that arrive before that were mishandled. Command callbacks like `on_qmp_complete()` crashed on a NULL bridge assertion. Also, `JOB_STATUS_CHANGE` events were dropped: they drive the boot-time blockdev-create continuation for `--ephemeral`. This only showed when the varlink setup failed, e.g. with a too long runtime directory path. Tearing down the bridge then failed the pending commands, and vmspawn aborted with an assertion instead of exiting with the error. Both were introduced with commits882049362dand1a7b6fd9dd. To fix this, set the `userdata` and bind the event callback when creating the bridge. The bridge itself handles the events that drive its own state (job continuations, `DEVICE_DELETED`), and forwards the others to a callback that the varlink server binds for its event subscribers. Signed-off-by: Martin Pitt <martin@amutable.com> (cherry picked from commit 2cac293064215d3e4f5ed92a1e898f89e6ac4629)
System and Service Manager
Details
Most documentation is available on systemd's website.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS, and also repositories with packages built from the latest stable release