Luca Boccassi
f8a1943758
Without CAP_SYS_ADMIN and without the 'user_subvol_rm_allowed' mount option, BTRFS_IOC_SNAP_DESTROY is rejected with EPERM (or EROFS for a read-only subvolume), so rm_rf_subvolume() left subvolumes behind. test-btrfs thus accumulated leftover subvolumes in /var/tmp on every unprivileged run on a btrfs filesystem. An unprivileged owner can however clear the RDONLY flag, empty a subvolume and rmdir() it. So clear the RDONLY flag on EPERM/EACCES too (not just EROFS) to leave the subvolume writable, and let rm_rf() fall through on EPERM/EACCES to empty the subvolume recursively and rmdir() it, matching what rm_rf_at() already did. Fixes https://github.com/systemd/systemd/issues/42674
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, and also repositories with packages built from the latest stable release