Adrian Vovk
bf3f4d16d6
Previously, mangle_filename would write the null terminator, but then wouldn't increment the pointer. Thus, the pad4 call that comes immediately after mangle_filename would trample over the null terminator that mangle_filename wrote. Since the padding is all 0s, this happened to work for the filenames it was tested for However, in some cases, this would cause the pointer to be a different position than predicted. Basically, the predicted size would be one byte bigger than the actual size (the missing null terminator). Usually, this disappeared into the alignment padding at the end of the buffer, but if the buffer was already unexpectedly aligned (b/c it was a byte shorter than expected), this would cause assertion failures. Also, the c_namesize field in the cpio header was incorrect. It didn't include the null terminator, as required by the spec.
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 or join our IRC channel.
Stable branches with backported patches are available in the stable repo.