Bug 1388635
| Summary: | glibc: nss_db: get*ent crashes without preceding set*ent | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marcel Kolaja <mkolaja> |
| Component: | glibc | Assignee: | Carlos O'Donell <codonell> |
| Status: | CLOSED ERRATA | QA Contact: | Michael Petlan <mpetlan> |
| Severity: | medium | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.2 | CC: | alanm, ashankar, chwood, codonell, cww, fhirtz, fkrska, fweimer, mcermak, mnewsome, mpetlan, pfrankli |
| Target Milestone: | rc | Keywords: | Patch, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | glibc-2.17-157.el7_3.1 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, Name Service Switch (NSS) module using hash-indexed files (nss_db)initialized itself incorrectly. Consequently, when nss_db module was enabled and any of the get*ent functions, such as getservent(), was called before a
corresponding set*ent call, the application that called get*ent terminated unexpectedly. With this update, nss_db initialization sequence is fixed. As a result, calling get*ent functions without first calling set*ent works as
expected, and the application no longer crashes.
|
Story Points: | --- |
| Clone Of: | 1213603 | Environment: | |
| Last Closed: | 2016-12-06 17:05:35 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: | |||
| Bug Depends On: | 1213603 | ||
| Bug Blocks: | |||
|
Description
Marcel Kolaja
2016-10-25 19:35:31 UTC
Reproduced with: glibc-2.17-157.el7 Verified with: glibc-2.17-157.el7_3.1 VERIFIED. 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-2861.html |