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.
Bug 2117203 - RHEL-9.1: loop-overlay test failed
Summary: RHEL-9.1: loop-overlay test failed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: util-linux
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Karel Zak
QA Contact: Radka Brychtova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-10 10:03 UTC by Karel Zak
Modified: 2022-11-15 13:22 UTC (History)
0 users

Fixed In Version: util-linux-2.37.4-6.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 11:23:24 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-130816 0 None None None 2022-08-10 10:11:58 UTC
Red Hat Product Errata RHBA-2022:8404 0 None None None 2022-11-15 11:23:32 UTC

Description Karel Zak 2022-08-10 10:03:54 UTC 
Upstream tests output:

util-linux-2.37.4-5.el9:

   libmount: loop overlay                   ...
diff-{{{
--- /dev/null	2022-08-10 04:17:46.680000000 -0400
+++ /var/str/source/tests/output/libmount/loop-overlay.err	2022-08-10 04:22:55.378604941 -0400
@@ -0,0 +1,4 @@
+mount: /var/str/source/tests/output/libmount/loop-overlay-mnt-1: overlapping loop device exists for /var/str/source/tests/output/libmount/loop-overlay.img.
+mount: /var/str/source/tests/output/libmount/loop-overlay-mnt-2: overlapping loop device exists for /var/str/source/tests/output/libmount/loop-overlay.img.
+umount: /var/str/source/tests/output/libmount/loop-overlay-mnt-1: not mounted.
+umount: /var/str/source/tests/output/libmount/loop-overlay-mnt-2: not mounted.
}}}-diff

Note that there is no change in mount or loopdev code in 9.1. The previous build (util-linux-2.37.4-3.el9) has been successful. The difference is kernel (5.14.0-58.el9.x86_64, now 5.14.0-139.el9.x86_64).

Three upstream patches may fix the issue (a race between loop autoclear and mount):

3e1fc3bbee99384cf43c2677cf77756a0ef002c0 mount: Fix race in loop device reuse code
fb4b6b11544df405fb0f486b399938a8ee3f03e6 loopdev: Properly translate errors from ul_path_read_*()
562990b5520ec8331dab25d139af8cb15d37e5a1 loopdev: Do not treat errors when detecting overlap as fatal
Comment 2 Karel Zak 2022-08-15 12:44:54 UTC 
The upstream patches are unnecessary. It seems enough is to improve the test (add "udevadm settle" to wait for udevd). Fixed.
Comment 9 errata-xmlrpc 2022-11-15 11:23:24 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (util-linux bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:8404
Note You need to log in before you can comment on or make changes to this bug.