Bug 1298095 - 1.2.11.15-68.el6_7 ns-slapd crash in ipa context - c_mutex lock memory corruption and self locks
Summary: 1.2.11.15-68.el6_7 ns-slapd crash in ipa context - c_mutex lock memory corrup...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base
Version: 6.7
Hardware: x86_64
OS: Linux
urgent
high
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
URL:
Whiteboard:
: 1363883 (view as bug list)
Depends On: 1296694
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-13 09:00 UTC by Jan Kurik
Modified: 2019-11-14 07:19 UTC (History)
6 users (show)

Fixed In Version: 389-ds-base-1.2.11.15-70.el6_7
Doc Type: Bug Fix
Doc Text:
Prior to this update, fixing a deadlock in the asynchronous simple paged results requests caused another self deadlock due to a regression. To address this problem, a simple PR_Lock on a connection object has been replaced with a re-entrant PR_Monitor. As a result, the self deadlock no longer occurs.
Clone Of: 1296694
Environment:
Last Closed: 2016-03-22 14:47:14 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0468 0 normal SHIPPED_LIVE 389-ds-base bug fix update 2016-03-22 18:46:51 UTC

Description Jan Kurik 2016-01-13 09:00:20 UTC 
This bug has been copied from bug #1296694 and has been proposed
to be backported to 6.7 z-stream (EUS).
Comment 6 errata-xmlrpc 2016-03-22 14:47:14 UTC 
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-0468.html
Comment 7 German Parente 2016-08-04 16:33:23 UTC 
*** Bug 1363883 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.