Bug 1702740
| Summary: | ns-slapd craches on IPA Servers throughout the customer's topology | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Josip Vilicic <jvilicic> |
| Component: | 389-ds-base | Assignee: | thierry bordaz <tbordaz> |
| Status: | CLOSED ERRATA | QA Contact: | RHDS QE <ds-qe-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.6 | CC: | cobrown, ebock, gerases, lkrispen, mreynolds, msauton, nkinder, pasik, rmeggins, spichugi, tbordaz, tmihinto, vashirov |
| Target Milestone: | rc | ||
| Target Release: | 7.7 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | sync-to-jira | ||
| Fixed In Version: | 389-ds-base-1.3.9.1-8.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: |
Cause: A worker thread can read/poll a connection while another worker thread can write/poll the same connection. The PR_Poll is not thread safe
Consequence: flow of async operations can lead to two threads polling the same connection, stepping on each other and crashing the server
Fix: make sure that the read/poll thread and write/pool thread are synchronized using a lock
Result: flow of asynch operations is not crashing the server.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-06 12:59:17 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 2
mreynolds
2019-05-09 15:25:52 UTC
Hi, The version of 'nspr' I saw in the sosreport is the following: nspr-4.19.0-1.el7_5.x86_64 If any more info is needed, please let us know and I will provide it to the Bugzilla ticket. Corey Brown Build tested: 389-ds-base-1.3.9.1-10.el7.x86_64 There is no identified reproducer. The build passes acceptance tests. Marking as VERIFIED, SanityOnly. 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://access.redhat.com/errata/RHBA-2019:2152 |