Back to bug 1810146
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2020-03-04 15:43:14 UTC | Pool ID | sst_platform_tools_rhel_8 | |
| Carlos O'Donell | 2020-03-04 15:43:58 UTC | Doc Type | If docs needed, set a value | Bug Fix |
| Sergey Kolosov | 2020-03-13 14:31:44 UTC | CC | skolosov | |
| Carlos O'Donell | 2020-04-02 02:16:47 UTC | Depends On | 1819986 | |
| Carlos O'Donell | 2020-04-02 02:45:57 UTC | Assignee | glibc-bugzilla | codonell |
| Carlos O'Donell | 2020-04-03 02:31:18 UTC | Status | NEW | MODIFIED |
| Fixed In Version | glibc-2.28-112.el8 | |||
| errata-xmlrpc | 2020-04-07 14:18:46 UTC | Status | MODIFIED | ON_QA |
| Florian Weimer | 2020-05-12 13:35:50 UTC | Doc Text | Cause: The getaddrinfo function in glibc does not release the internal resolver context after a memory allocation failure. Consequence: Automatic reloading of /etc/resolv.conf is blocked for the reminder of the life-time of the calling thread, and memory can be leaked. Fix: An additional resolver context release operation was added to the error handling path. Result: getaddrinfo tries to reload /etc/resolv.conf with new configuration values even after an intermittent memory allocation failure. |
|
| Lucie Vařáková | 2020-06-16 10:48:25 UTC | CC | lmanasko | |
| Docs Contact | lvaleeva | |||
| Levi | 2020-06-16 15:10:26 UTC | Docs Contact | lvaleeva | pkovar |
| Petr Kovar | 2020-06-25 12:57:05 UTC | Docs Contact | pkovar | zzoubkov |
| Zuzana Zoubkova | 2020-09-04 14:17:38 UTC | Flags | needinfo?(codonell) | |
| Florian Weimer | 2020-09-07 10:17:20 UTC | Flags | needinfo?(codonell) | |
| Zuzana Zoubkova | 2020-09-15 10:58:59 UTC | Doc Text | Cause: The getaddrinfo function in glibc does not release the internal resolver context after a memory allocation failure. Consequence: Automatic reloading of /etc/resolv.conf is blocked for the reminder of the life-time of the calling thread, and memory can be leaked. Fix: An additional resolver context release operation was added to the error handling path. Result: getaddrinfo tries to reload /etc/resolv.conf with new configuration values even after an intermittent memory allocation failure. | .`getaddrinfo` now correctly handles a memory allocation failure Previously, after a memory allocation failure, the `getaddrinfo` function of the GNU C Library `glibc` did not release the internal resolver context. As a consequence, `getaddrinfo` was not able to reload the `/etc/resolv.conf` file for the rest of the lifetime of the calling thread, resulting in a possible memory leak. This update modifies the error handling path with an additional release operation for the resolver context. As a result, `getaddrinfo` reloads `/etc/resolv.conf` with new configuration values even after an intermittent memory allocation failure. |
| Sergey Kolosov | 2020-09-22 10:40:55 UTC | Status | ON_QA | VERIFIED |
| Florian Weimer | 2020-10-05 08:14:03 UTC | CC | sipoyare | |
| Red Hat One Jira (issues.redhat.com) | 2020-11-01 07:35:34 UTC | Link ID | Red Hat Issue Tracker - Private RHELPLAN-38620 | |
| errata-xmlrpc | 2020-11-03 00:41:38 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2020-11-04 01:33:21 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2020-11-04 01:33:21 UTC | |||
| errata-xmlrpc | 2020-11-04 01:33:43 UTC | Link ID | Red Hat Product Errata RHSA-2020:4444 | |
| Pavel Najman | 2021-09-17 12:19:35 UTC | Pool ID | sst_platform_tools_rhel_8 | sst_pt_gcc_glibc_rhel_8 |
| Mark O'Brien | 2023-07-18 14:30:35 UTC | Pool ID | sst_pt_glibc_rhel_8 | sst_pt_libraries_rhel_8 |
Back to bug 1810146