Philip Withnall
0b3eeb1547
If a varlink method takes a struct/object as a parameter, and it’s marked as `SD_JSON_MANDATORY`, and it has an optional field inside it which is *not* marked as `SD_JSON_MANDATORY`, we want to not require that field to be set. Previously, due to using the `merged_flags` from both the mandatory struct and the optional field, `SD_JSON_MANDATORY` was effectively always set on the optional field even if we didn’t want it. This resulted in an error being emitted if the mandatory struct was provided in a varlink call, but without the optional field. Fix that by validating the field’s presence only against its own flags and not also the flags of its parent. Adds a unit test to prevent regressions.
System and Service Manager
Details
Most documentation is available on systemd's web site.
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