Bug 1699958
Summary: | Perl inet_aton is not thread-safe [perl:5.24] | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Petr Pisar <ppisar> |
Component: | perl-Socket | Assignee: | perl-maint-list |
Status: | CLOSED ERRATA | QA Contact: | RHEL CS Apps Subsystem QE <rhel-cs-apps-subsystem-qe> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | bnater, jorton, lmanasko, mkyral, pandrade, perl-maint-list, ppisar, rhel-stacks-subsystem-qe |
Target Milestone: | rc | Keywords: | Patch |
Target Release: | 8.0 | Flags: | pm-rhel:
mirror+
|
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | perl-5.24-8010020190416105253.3af8e029 | Doc Type: | Bug Fix |
Doc Text: |
.`Socket::inet_aton()` can now be used from multiple threads safely
Previously, the `Socket::inet_aton()` function, used for resolving a domain name from multiple Perl threads, called the unsafe `gethostbyname()` `glibc` function. Consequently, an incorrect IPv4 address was occasionally returned, or the Perl interpreter terminated unexpectedly. With this update, the `Socket::inet_aton()` implementation has been changed to use the thread-safe `getaddrinfo()` `glibc` function instead of `gethostbyname()`. As a result, the `inet_aton()` function from Perl `Socket` module can be used from multiple threads safely.
|
Story Points: | --- |
Clone Of: | 1699793 | Environment: | |
Last Closed: | 2019-11-05 20:44:41 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: |
Description
Petr Pisar
2019-04-15 13:16:51 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/RHBA-2019:3337 |