Chris Morin
08f9e80b3f
The thread launched in journal_file_set_offline() accesses a memory mapped file, so it needs to handle SIGBUS. Leave SIGBUS unblocked on the offlining thread so that it uses the same handler as the main thread. The result of triggering SIGBUS in a thread where it's blocked is undefined in Linux. The tested implementations were observed to cause the default handler to run, taking down the whole journald process. We can leave SIGBUS unblocked in multiple threads since it's handler is thread-safe. If SIGBUS is sent to the journald process asynchronously (i.e. with kill, sigqueue, or raise), either thread handling it will result in the same behavior: it will install the default handler and reraise the signal, killing the process. Fixes: #12042
systemd - System and Service Manager
Details
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 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.