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.

suppose I setup chrooted environment as follow:
1. mount some losetup into /test.
2. mount --bind /proc, /sys, /dev and so on into /test/$item

when reboot command is passed, system will start __umount_loopback_loop()  from /etc/init.d/functions.

It will not be able to unmount /test because mountpoint is busy (/test/proc is mounted)

I think, __umount_loopback_loop() should detect situation when "fuser" return empty list and still can not umount.

The problem is in the lack of recursive umount functional (see http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg199613.html)
Other problem is lack of testing for underlying mountpoints in fuser tool.


As the fast way to umount /test when fuser say nothing, is to use umount -l.
I discover, that umount -l will recursively unmount submounts.

Changing this to cover all cases would be too much of a change for an update release - this should be fixed properly in the next major release.

Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.