Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 511265[details]
Patch - fix null cache deadlock
Description of problem:
When reloading maps that include a combination of direct and indirect
maps it is possible for automount to deadlock due to incorrect lock
ordering.
How reproducible:
Occasionally.
Steps to Reproduce:
Reported upstream.
I'm not able to reproduce the problem at the moment.
check patch autofs-5.0.5-fix-null-cache-deadlock.patch apply is sane and as per below comment from dev:
The problem described by this bug is fairly obvious once the issue is recognised. The fix is not quite so obvious but is a small change and has been verified by the reporter upstream.
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2011-1723.html
Created attachment 511265 [details] Patch - fix null cache deadlock Description of problem: When reloading maps that include a combination of direct and indirect maps it is possible for automount to deadlock due to incorrect lock ordering. How reproducible: Occasionally. Steps to Reproduce: Reported upstream. I'm not able to reproduce the problem at the moment.