Zbigniew Jędrzejewski-Szmek
08d8224c0a
path_is_root_at() is supposed to detect if the inode referenced by the specified fd is the "root inode". For that it checks if the inode and its parent are the same inode and the same mount. Traditionally this check was correct. But these days we actually have detached mounts (i.e. those returned by fsmount() and related calls), whose root inode also behaves like that. Our uses for path_is_root_at() use the function to detect if an absolute path would be identical to a relative path based on the specified fd (sepifically: chaseat()), which goes really wrong if used on a detached mount. hence, let's adjust the function a bit, and let's go by path to "/" to check if the referenced inode is the actual root inode in our chroot.
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