Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1370630
Summary: | glibc: nss_db: Endless loop in services database processing | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Frank Hirtz <fhirtz> | ||||
Component: | glibc | Assignee: | Florian Weimer <fweimer> | ||||
Status: | CLOSED ERRATA | QA Contact: | Sergey Kolosov <skolosov> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 7.2 | CC: | aheverle, ashankar, codonell, fweimer, mcermak, mnewsome, mpetlan, pfrankli, skolosov | ||||
Target Milestone: | rc | Keywords: | Patch, ZStream | ||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | glibc-2.17-158.el7 | Doc Type: | Bug Fix | ||||
Doc Text: |
Cause: The nss_db Name Service Switch module does not properly handle a protocol mismatch during lookups in the service database.
Consequence: Lookups in the service database can enter an infinite loop.
Fix: The nss_db code which looks up service entries has been fixed to deal with protocol mismatches and proceed with the next entry.
Result: Service entries can be found properly, without a hang.
|
Story Points: | --- | ||||
Clone Of: | |||||||
: | 1388639 (view as bug list) | Environment: | |||||
Last Closed: | 2017-08-01 18:09:25 UTC | Type: | Bug | ||||
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: | |||||||
Bug Blocks: | 1388639, 1390370 | ||||||
Attachments: |
|
Description
Frank Hirtz
2016-08-26 20:24:23 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://access.redhat.com/errata/RHSA-2017:1916 |