Lennart Poettering
9151a60a4e
As usual, we need to protect ourselves against concurrent modification of journal files. We a pretty good at that these days when reading journal files. But journal_file_copy_entry() so far wasn't too good with that. journal_file_append_data() so far returned EINVAL when you pass invalid data to it. Since we pass the source data as-is in there, it's going to fail if the journal source file is slightly invalid due to a concurrent update. Hence, we need to validate data gracefully here that we think comes from a safe place, because actually it doesn't, it's directly copied from an unsafe journal file. Hence, let's introduce a clear error code here, and look for it in journal_file_copy_entry(), and handle it gracefully. Pretty sure this fixes #33372, but it's a race, so I don't know for sure. If this remains reproducible we need to look at this again. Fixes: #33372
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