We have a number of issues where oss-fuzz reports input-independent crashes of fuzz-journal-remote. Instead of asserting that stuff that allocated fds and memory never fails, let's instead just return an error. https://oss-fuzz.com/testcase-detail/4791099424112640 https://oss-fuzz.com/testcase-detail/4531912477638656 I don't see any docs as to whether LLVMFuzzerTestOneInput() is allowed to return non-zero. Propagating the error code is easiest, so let's just do that. If it turns out that this causes oss-fuzz to still report a failure, we can suppress that later.
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 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 or join our IRC channel.
Stable branches with backported patches are available in the stable repo.
