Daan De Meyer
2fd17cb9ea
Several places write a buffer at an offset with a single pwrite() or pwritev(), and fail if the call writes less than the whole buffer. The lock file of a dynamic user is then truncated to the bytes written, so it keeps a cut-off user name. memfd_new_and_seal() fails for data larger than one write() call accepts, which is about 2 GiB on Linux. The other callers return -EIO, and lose the error that another write would report, such as ENOSPC. Use pwrite_full(), which keeps writing until the whole buffer is written or a write fails. The lock file of a dynamic user is written from two buffers and uses pwritev_full() instead. repart writes the verity signature with lseek() and loop_write(). It uses pwrite_full() as well, which does not move the file offset.
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