Yu WatanabeandEric Curtin
13d89ece2d
Previously, bpf_restrict_fsaccess_prepare() is called twice in bpf_restrict_fsaccess_setup(). One by through bpf_restrict_fsaccess_supported() and one by itself directly. In PID1, bpf_restrict_fsaccess_prepare() was only called by bpf_restrict_fsaccess_setup(), hence it is not necessary to exist as a separated function. bpf_restrict_fsaccess_prepare() loads BPF program(s), hence it is slightly slow operation. Let's avoid redundant loading of BPF programs by merging bpf_restrict_fsaccess_supported() into bpf_restrict_fsaccess_setup(). Co-authored-by: Eric Curtin <eric.curtin@docker.com>
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