Comment 7 for bug 1640823

Martin Pitt (pitti) wrote :

I successfully ran the test case against ubuntu20.9 in -proposed. I also verified that using losetup and mount on loop devices still works:

$ sudo losetup -f --show debian-stretch-DI-alpha7-amd64-netinst.iso
$ sudo mount /dev/loop0 /mnt
mount: block device /dev/loop0 is write-protected, mounting read-only
$ ls /mnt
autorun.inf debian [...]

With the -proposed version, losetup -f also succeeds to use /dev/loop-control, so you can do the above a few times and it works with /dev/loop12 too. When moving /dev/loop-control out of the way, the above also works up to loop7, and then errors out with "losetup: could not find any free loop device" as expected. "losetup -a" correctly shows the bound devices/files.