Bug 1020486
Summary: | glibc getnameinfo call fails when many PTR records are associated with an IP | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Blake <blake.a.hudson> | ||||
Component: | glibc | Assignee: | Siddhesh Poyarekar <spoyarek> | ||||
Status: | CLOSED ERRATA | QA Contact: | Arjun Shankar <ashankar> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 5.9 | CC: | ashankar, codonell, fweimer, law, mcermak, mfranc, mnewsome, pfrankli, spoyarek | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | glibc-2.5-121 | Doc Type: | Bug Fix | ||||
Doc Text: |
The getnameinfo function would incorrectly fail on a reverse lookup when there are a large number of PTR records are associated with the IP address being looked up. With this fix, getnameinfo now correctly returns one of the PTR records as the response.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2014-09-16 00:25:49 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: | 1049888 | ||||||
Attachments: |
|
Description
Blake
2013-10-17 18:37:16 UTC
Thanks for submitting this issue. We'll consider this bug while we scope issues to fix for the next release. Just an FYI from the planning call. This will be ack'd by PM and is expected to be within QE capacity for RHEL 5.11. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release. 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/RHBA-2014-1213.html |