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 1947589[details]
core file of deadlocked automount process
Description of problem:
A deadlock can occur while reading amd maps, leading to hung automount process.
Version-Release number of selected component (if applicable):
autofs-5.1.4-88
How reproducible:
Unknown
Steps to Reproduce:
the 'reproducer' in bz2139504 can sometimes hit this deadlock
Actual results:
deadlock leads to unresponsive automount process
Expected results:
no deadlock
Additional info:
core file attached
(In reply to Frank Sorenson from comment #0)
> Created attachment 1947589[details]
> core file of deadlocked automount process
>
> Description of problem:
>
> A deadlock can occur while reading amd maps, leading to hung automount
> process.
>
>
>
> Version-Release number of selected component (if applicable):
>
> autofs-5.1.4-88
>
>
>
> How reproducible:
>
> Unknown
>
>
> Steps to Reproduce:
>
> the 'reproducer' in bz2139504 can sometimes hit this deadlock
I think the reproducer may be encountering this problem more than you realise.
The way I discovered it was running the reproducer and terminating the test
before error conditions started occurring then waiting for the mounts to expire.
Fairly often I would see the mounts one level below the top level not able to
expire away, something I've started seeing for a while now, and looking at back
traces showed there was actually a deadlock occurring. Something I have missed
completely while working on this problem so far.
Ian