Bug 1288447
| Summary: | deadlock in ipa context with 389-ds-base-1.3.3.1-20.el7_1.x86_64 in gssapi | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jan Kurik <jkurik> |
| Component: | cyrus-sasl | Assignee: | Jakub Jelen <jjelen> |
| Status: | CLOSED ERRATA | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.1 | CC: | abokovoy, ccoursey, cww, ebenes, ekeck, gagriogi, gparente, jjelen, jkurik, ksrot, lmiksik, mkosek, msauton, nhosoi, nkinder, pkis, plautrba, rmeggins |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | cyrus-sasl-2.1.26-20.el7_2 | Doc Type: | Bug Fix |
| Doc Text: |
When using the Cyrus SASL library (cyrus-sasl) Generic Security Services API (GSSAPI) plug-in, all connections shared a single lock for both server and client implementations. As a consequence, a deadlock in the cyrus-sasl GSSAPI plug-in caused the whole Directory Server to become unresponsive when both outgoing replication and incoming client connections used SASL GSSAPI. This update introduces per-thread locks, which minimizes the required synchronization and prevents a deadlock from occurring if some threads are blocked. As a result, the Directory Server is now able to reliably handle concurrent connections that use the cyrus-sasl GSSAPI plug-in.
|
Story Points: | --- |
| Clone Of: | 1263017 | Environment: | |
| Last Closed: | 2016-02-16 10:39:53 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1263017 | ||
| Bug Blocks: | 1203710 | ||
|
Description
Jan Kurik
2015-12-04 09:15:04 UTC
*** Bug 1293945 has been marked as a duplicate of this bug. *** 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. https://rhn.redhat.com/errata/RHBA-2016-0178.html |