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 1263017 - deadlock in ipa context with 389-ds-base-1.3.3.1-20.el7_1.x86_64 in gssapi
Summary: deadlock in ipa context with 389-ds-base-1.3.3.1-20.el7_1.x86_64 in gssapi
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cyrus-sasl
Version: 7.1
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Jakub Jelen
QA Contact: Stanislav Zidek
URL:
Whiteboard:
Depends On:
Blocks: 1203710 1288447
TreeView+ depends on / blocked
 
Reported: 2015-09-14 23:05 UTC by Marc Sauton
Modified: 2019-10-10 10:11 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: All the connections over cyrus-sasl using GSSAPI plugin were using one shared lock for both server and client implementations. Consequence: Deadlock in cyrus-sasl GSSAPI plugin caused whole directory server stop responding when outgoing replication uses SASL GSSAPI and incoming client connection uses SASL GSSAPI. Fix: Introduction of per-thread locks minimizes the required synchronization and prevents deadlock if some threads are blocked. Result: The directory server is able to handle reliably concurrent connections using GSSAPI plugin in cyrus-sasl.
Clone Of:
: 1288447 (view as bug list)
Environment:
Last Closed: 2016-12-09 15:17:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
stacktrace.1442262078.txt - was collected with missing debuginfo, just shows deadlocks (89.17 KB, text/plain)
2015-09-14 23:09 UTC, Marc Sauton
no flags Details

Description Marc Sauton 2015-09-14 23:05:41 UTC
Description of problem:

deadlock in ipa context with 389-ds-base-1.3.3.1-20.el7_1.x86_64 in gssapi

need pstack review

there are several threads with a trace similar to this:

Thread 33 (Thread 0x7f0fecd58700 (LWP 2420)):
#0  0x00007f1018682f7d in __lll_lock_wait () from /lib64/libpthread.so.0
#1  0x00007f101867ed68 in _L_lock_975 () from /lib64/libpthread.so.0
#2  0x00007f101867ed11 in pthread_mutex_lock () from /lib64/libpthread.so.0
#3  0x00007f1018cd5cb9 in PR_Lock () from /lib64/libnspr4.so
#4  0x00007f101adc7a99 in nssasl_mutex_lock ()
#5  0x00007f101301430c in gssapi_decode_packet () from /usr/lib64/sasl2/libgssapiv2.so
#6  0x00007f1018aabb25 in _plug_decode () from /lib64/libsasl2.so.3
#7  0x00007f1013014826 in gssapi_decode () from /usr/lib64/sasl2/libgssapiv2.so
#8  0x00007f1018aa15bd in sasl_decode () from /lib64/libsasl2.so.3
#9  0x00007f101adc773a in sasl_io_recv ()
#10 0x00007f101adb78f1 in connection_read_operation ()
#11 0x00007f101adb88df in connection_threadmain ()
#12 0x00007f1018cdb7bb in _pt_root () from /lib64/libnspr4.so
#13 0x00007f101867cdf5 in start_thread () from /lib64/libpthread.so.0
#14 0x00007f10183aa1ad in clone () from /lib64/libc.so.6


Version-Release number of selected component (if applicable):
389-ds-base-1.3.3.1-20.el7_1.x86_64
redhat-release-server-7.1-1.el7.x86_64


How reproducible:
N/A


Steps to Reproduce:
1. N/A
2.
3.


Actual results:
ns-slapd hang / deadlock as per pstack


Expected results:


Additional info:

Comment 1 Marc Sauton 2015-09-14 23:09:46 UTC
Created attachment 1073444 [details]
stacktrace.1442262078.txt - was collected with missing debuginfo, just shows deadlocks

Comment 55 Marcel Kolaja 2016-12-09 15:17:25 UTC
The fix for this bug has been delivered in RHEL 7.2.z and this component has not been updated in RHEL 7.3. RHEL 7.3 contains the fix from RHEL 7.2.z. Therefore, this bug has been closed as CURRENTRELEASE.


Note You need to log in before you can comment on or make changes to this bug.