39adecfcd8
When a child process exits normally (si_code == CLD_EXITED), siginfo.si_status contains the exit code. When it is killed by a signal (si_code == CLD_KILLED or CLD_DUMPED), si_status contains the signal number. However, assert_signal_internal() returns si_status blindly. This causes exit codes to be misinterpreted as signal numbers. This allows failing tests to silently pass if their exit code numerically coincides with the expected signal. For example, a test expecting SIGABRT (6) would incorrectly pass if the child simply exited with status 6 instead of being killed by a signal. Fix this by checking si_code. Only return si_status as a signal number if the child was actually killed by a signal (CLD_KILLED or CLD_DUMPED). If the child exited normally (CLD_EXITED), return 0 to indicate that no signal occurred.
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