Back to bug 1749439
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2019-09-05 15:45:26 UTC | Pool ID | sst_platform_tools_rhel_8 | |
| Carlos O'Donell | 2019-09-05 15:46:42 UTC | Keywords | Patch, Triaged | |
| Florian Weimer | 2019-10-22 13:51:19 UTC | Status | NEW | ASSIGNED |
| Target Release | 8.0 | 8.2 | ||
| Carlos O'Donell | 2019-10-24 03:33:32 UTC | Blocks | 1746918 | |
| Carlos O'Donell | 2019-10-24 13:51:38 UTC | Assignee | glibc-bugzilla | fweimer |
| Ondřej Lysoněk | 2019-11-07 12:11:59 UTC | Flags | needinfo?(fweimer) | |
| Florian Weimer | 2019-11-07 12:47:06 UTC | Flags | needinfo?(fweimer) | |
| Florian Weimer | 2019-11-07 16:23:28 UTC | Blocks | 1741515 | |
| Florian Weimer | 2019-11-13 13:14:26 UTC | Status | ASSIGNED | MODIFIED |
| Fixed In Version | glibc-2.28-90.el8 | |||
| errata-xmlrpc | 2019-11-16 21:55:39 UTC | Status | MODIFIED | ON_QA |
| Florian Weimer | 2019-12-17 17:15:58 UTC | Doc Text | Cause: A timeout during a lock acquisition in pututxline corrupts internal state of the utmp subsystem. Consequence: Unused entries are added to the utmp subsystem, increasing its size substantially. Fix: The timeout handling has been reworked and the file pointer is tracked correctly now. Result: Repeated putuxline calls after EINTR/EAGAIN do not result in stale entries, and the file size growth is now limited. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Sergey Kolosov | 2020-02-27 14:44:33 UTC | CC | skolosov | |
| Sergey Kolosov | 2020-03-01 18:10:50 UTC | Status | ON_QA | VERIFIED |
| Oss Tikhomirova | 2020-03-20 18:27:32 UTC | CC | otikhomi | |
| Docs Contact | otikhomi | |||
| Oss Tikhomirova | 2020-03-30 10:25:56 UTC | Docs Contact | otikhomi | |
| Petr Kovar | 2020-03-30 15:19:30 UTC | Docs Contact | zzoubkov | |
| Florian Weimer | 2020-04-08 16:41:50 UTC | Doc Text | Cause: A timeout during a lock acquisition in pututxline corrupts internal state of the utmp subsystem. Consequence: Unused entries are added to the utmp subsystem, increasing its size substantially. Fix: The timeout handling has been reworked and the file pointer is tracked correctly now. Result: Repeated putuxline calls after EINTR/EAGAIN do not result in stale entries, and the file size growth is now limited. | Cause: A timeout during a lock acquisition in pututxline corrupts internal state of the utmp subsystem before the function returns with an EINTR or EAGAIN error code. Consequence: Unused entries are added to the utmp subsystem, increasing its size substantially. Fix: The timeout handling has been reworked and the file pointer is tracked correctly now. Result: Repeated putuxline calls after the function has reported an EINTR or EAGAIN error do not result in stale entries, and the file size growth is now limited. |
| Zuzana Zoubkova | 2020-04-17 11:59:05 UTC | Flags | needinfo?(fweimer) | |
| Florian Weimer | 2020-04-17 12:01:37 UTC | Flags | needinfo?(fweimer) | |
| Zuzana Zoubkova | 2020-04-17 14:13:06 UTC | Doc Text | Cause: A timeout during a lock acquisition in pututxline corrupts internal state of the utmp subsystem before the function returns with an EINTR or EAGAIN error code. Consequence: Unused entries are added to the utmp subsystem, increasing its size substantially. Fix: The timeout handling has been reworked and the file pointer is tracked correctly now. Result: Repeated putuxline calls after the function has reported an EINTR or EAGAIN error do not result in stale entries, and the file size growth is now limited. | .Repeated `pututxline` calls following `EINTR` or `EAGAIN` error no longer corrupt the `utmp` file When the `pututxline` function tries to acquire a lock and does not succeed in time, the function returns with `EINTR` or `EAGAIN` error code. Previously in this situation, if `pututxline` was called immediately again and managed to obtain the lock, it did not use an already-allocated matching slot in the `utmp` file, but added another entry instead. As a consequence, these unused entries increased the size of the `utmp` file substantially. This update fixes the issue, and the entries are added to the `utmp` file correctly now. |
| errata-xmlrpc | 2020-04-28 00:32:14 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2020-04-28 16:50:19 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2020-04-28 16:50:19 UTC | |||
| errata-xmlrpc | 2020-04-28 16:50:46 UTC | Link ID | Red Hat Product Errata RHSA-2020:1828 | |
| Pavel Najman | 2021-09-17 12:19:35 UTC | Pool ID | sst_platform_tools_rhel_8 | sst_pt_gcc_glibc_rhel_8 |
| Red Hat One Jira (issues.redhat.com) | 2021-09-17 12:24:23 UTC | Link ID | Red Hat Issue Tracker RHELPLAN-28582 | |
| 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 1749439