Lennart Poettering
b8ee13613c
When systemd-loop@.service is instantiated for a block device (e.g. a CD-ROM drive, which is the primary usecase now that --relax is used), %f resolves to the backing block device rather than to the loopback block device that was attached on top of it. In that case ExecStop= hence invoked --detach on a block device that is not a loopback device at all, which made loop_device_set_autoclear() a silent no-op, leaking the attachment. Hence, if --detach is passed a block device that is not a loopback block device itself, search for the loopback block device backed by it, the same way we already do for regular files. The kernel reports the backing inode for block device nodes too, so the same inode matching logic applies.
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