Bug 2026289
| Summary: | Crond runs into segfault when getdtablesize() returns a huge value. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Flos Qi Guo <qguo> |
| Component: | cronie | Assignee: | Jan Staněk <jstanek> |
| Status: | CLOSED ERRATA | QA Contact: | Jan Houska <jhouska> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.9 | CC: | fkrska, jhouska, jreznik, jstanek, opohorel, rmetrich, sbalasub, sbroz |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | cronie-1.4.11-24.el7_9 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: crond determined the amount of memory needed for some task based on the highest file descriptor number in use. In containers, this number could reach very high values.
Consequence: In containers, crond attempted to sometimes allocate several gigabytes of memory that was not actually needed; when that failed due to system limits or limitations, the program crashed.
Fix: An upstream change limiting the allocated memory size to sane(r) numbers was backported to this version of cronie.
Result: The crond no longer tries to allocate so much memory that it crashes, even in containers.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-01-11 17:35:52 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
Flos Qi Guo
2021-11-24 09:52:38 UTC
Patch imported into dist-git: http://pkgs.devel.redhat.com/cgit/rpms/cronie/commit/?h=rhel-7.9&id=4777be103a14d0161322733093b0f907810834b1 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 (cronie bug fix and enhancement update), 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-2022:0067 |