Bug 491419
| Summary: | leaking file descriptors | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Jeff Bastian <jbastian> | ||||||
| Component: | nss_ldap | Assignee: | Nalin Dahyabhai <nalin> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | BaseOS QE <qe-baseos-auto> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 4.7 | CC: | cward, dslehman, jeder, jplans, mhuth, mmarcini, rlerch, sputhenp, tao, vfalico | ||||||
| Target Milestone: | rc | Keywords: | OtherQA | ||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | nss_ldap-253-7.el4 | Doc Type: | Bug Fix | ||||||
| Doc Text: |
libnss-ldap does not pay attention to error codes received from LDAP servers. Therefore, if a process (such as nscd) attempted to re-open a connection after an LDAP server closed the connection, nss-ldap would previously leak file descriptors. A long-lived caller process would eventually run out of file descriptors and enter a loop, preventing any further name service activity. Nss-ldap now checks whether a socket has been closed by the LDAP server and avoids leaking file descriptors.
|
Story Points: | --- | ||||||
| Clone Of: | 428837 | Environment: | |||||||
| Last Closed: | 2009-05-18 20:20:00 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Jeff Bastian
2009-03-20 21:09:07 UTC
Created attachment 336123 [details]
patch to fix leaking file descriptors
This is a very slightly modified patch to apply to RHEL4 nss_ldap tree.
Created attachment 336124 [details]
patch to fix leaking file descriptors
Never mind, the original patch actually applies cleanly.
Support, Customers, I have uploaded test packages that should fix this issue below. These packages - if the issue reported can be confirmed as resolved - will be included in the upcoming 4.8 release. http://people.redhat.com/cward/4.8/nss_ldap/ The latest 4.8 Beta can be downloaded from RHN @ https://rhn.redhat.com/network/software/download_isos_full.pxt Please test and provide us with feedback ASAP. I can confirm that the test package fixes the issue for my customer in CRM 1881376. Now the customer is asking about getting some supported hotfix packages! Thanks Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: libnss-ldap does not pay attention to error codes received from LDAP servers. Therefore, if a process (such as nscd) attempted to re-open a connection after an LDAP server closed the connection, nss-ldap would previously leak file descriptors. A long-lived caller process would eventually run out of file descriptors and enter a loop, preventing any further name service activity. Nss-ldap now checks whether a socket has been closed by the LDAP server and avoids leaking file descriptors. 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-2009-0986.html |