RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
When I try to tear down a loop device backed by iso file, the iso file remains mounted despite udisksd claims that it deleted the loop device.

Version-Release number of selected component (if applicable):
udisks2-2.1.2-5.el7

How reproducible:
100%

Steps to Reproduce:
1. udisksctl loop-setup -f path/to/your/image.iso
2. udisksctl loop-delete -b /dev/loop0
3. udisksctl info -b /dev/loop0

Actual results:
iso file remains mounted

Expected results:
loop device is torn down

Additional info:

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Well, the way losetup works when deleting loop device is that it marks it as "autoclear", i.e. it automatically disappears when not used anymore (after unmount). I don't see any option to force removal or report an error.

`udisksctl loop-delete` acts the same way it succeeds as long losetup succeeds.

The only thing we can do is to unmount a mount when mounted through udisks; for mounts trigerred outside udisks we're not permitted to operate over them.

In any case, we should probably print a warning or something.