probe_gpt_boot_disk_needs_loop() sets ID_PART_GPT_AUTO_ROOT_DISK_NEEDS_LOOP for any whole disk that holds the boot ESP/XBOOTLDR but whose partition table the kernel cannot parse. Until now the udev rule turned that into a systemd-loop@.service for every block device. That is too broad: device-mapper devices also report kernel partition scanning as disabled, but their partitions are managed in userspace by kpartx (see 66-kpartx.rules). Setting up a loop device on top of them re-exposes the same partition table a second time and only causes trouble. Restrict the rule to optical drives, the one class that genuinely needs a kernel-side loop device (El Torito GPT sector size mismatch, or drives that do not support partition scanning) and that has no userspace partition manager of its own. Co-developed-by: Claude Fable 5 <noreply@anthropic.com>
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
