Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 730436 - use slapi_rwlock instead of NSPR PR_RWLock directly
use slapi_rwlock instead of NSPR PR_RWLock directly
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa (Show other bugs)
6.1
Unspecified Unspecified
high Severity unspecified
: rc
: ---
Assigned To: Rob Crittenden
Chandrasekar Kannan
:
Depends On: 730387 730395 743979
Blocks:
  Show dependency tree / graph
 
Reported: 2011-08-12 18:31 EDT by Dmitri Pal
Modified: 2015-01-04 18:50 EST (History)
9 users (show)

See Also:
Fixed In Version: ipa-2.1.1-1.el6
Doc Type: Bug Fix
Doc Text:
Cause: Under some rare circumstances certain operations may cause 389-ds to crash or not function properly. Consequence: 389-ds may not be available. Fix: NSPR read/write locks used by 389-ds are not re-entrant. The use of these locks were replaced with POSIX thread read-write locks instead in the IPA 389-ds plugins. Result: 389 should not crash due to re-entrant locks.
Story Points: ---
Clone Of: 730395
Environment:
Last Closed: 2011-12-06 13:29:49 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:1533 normal SHIPPED_LIVE Moderate: ipa security and bug fix update 2011-12-05 20:23:31 EST

  None (edit)
Description Dmitri Pal 2011-08-12 18:31:37 EDT 
+++ This bug was initially created as a clone of Bug #730395 +++

NSPR PR_RWLocks are not re-entrant.  389 is refactoring its code to provide and use slapi_rwlocks instead.  All freeipa plugins should be refactored to use the slapi_rwlock interface when it is available.
Comment 2 Dmitri Pal 2011-08-15 10:51:18 EDT 
https://fedorahosted.org/freeipa/ticket/1635
Comment 5 Rob Crittenden 2011-11-01 09:17:44 EDT 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: Under some rare circumstances certain operations may cause 389-ds to crash or not function properly.
Consequence: 389-ds may not be available.
Fix: NSPR read/write locks used by 389-ds are not re-entrant. The use of these locks were replaced with POSIX thread read-write locks instead in the IPA 389-ds plugins.
Result: 389 should not crash due to re-entrant locks.
Comment 6 Namita Soman 2011-11-08 08:08:02 EST 
Looks like this happens "Under some rare circumstances". Please suggest what is the good way to verify this bug
Comment 7 Rob Crittenden 2011-11-08 08:27:22 EST 
This may need to be validated by code review and general acceptance that the server is operating as before.
Comment 8 Michael Gregg 2011-11-08 14:03:45 EST 
verified:SanityOnly

This bug did not seem to pop up in any of our acceptance tests in the past 3 months.

Verified against:
bind-dyndb-ldap-0.2.0-7.el6.x86_64
ipa-server-2.1.3-8.el6.x86_64
Comment 9 errata-xmlrpc 2011-12-06 13:29:49 EST 
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.

http://rhn.redhat.com/errata/RHSA-2011-1533.html
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.