da65941c3e
Kernel API file systems typically use either "raw" or "seq_file" to implement their various interface files. The former are really simple (to point I'd call them broken), in that they have no understanding of file offsets, and return their contents again and again on every read(), and thus EOF is indicated by a short read, not by a zero read. The latter otoh works like a typical file: you read until you get a zero-sized read back. We have read_virtual_file() to read the "raw" files, and can use regular read_full_file() to read the "seq_file" ones. Apparently all files in the top-level /proc/ directory use 'seq_file'. but we accidentally used read_virtual_file() for them. Fix that. Also clarify in a comment what the rules are. Fixes: #36131
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