Bug 474181
Summary: | race in fork() | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Dominik Strasser <dominik.strasser> |
Component: | nss_ldap | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED ERRATA | QA Contact: | Ondrej Moriš <omoris> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.2 | CC: | dominik.strasser, dpal, drepper, fredrik.carlsson, jplans, mirko.fit, omoris, ralph, sean |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | nss_ldap-253-36.el5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-01-13 23:31:56 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: |
Description
Dominik Strasser
2008-12-02 17:35:04 UTC
Î've raised the priority because this issue leads to frequent hangs in our application. Hi, I can confirm this bug to, Usually its sshd that is affected but crond aswell as postfix can be affected. It's quite annoying bug and affects the function of the servers so it would be nice to have fixed ;) Regards Fredrik This is a bug in nss_ldap which is not part of glibc. Since fork can be called asynchronously it is not allowed to call any function that is not async-safe in the atfork handlers. nss_ldap's atfork handler calls free() which is not async-safe. Any news? Any news on this issue ? It is now 8 months old, and no reaction. This issue is more than 2 years old now. From an outside point of view the fix looks easy, find out why nss_ldap calls free() in atfork() and move the clean up to a safer location. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0097.html |