Bug 1419519
Summary: | Segfault in pam_cgroup.so | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Nikola Forró <nforro> | ||||
Component: | libcgroup | Assignee: | Nikola Forró <nforro> | ||||
Status: | CLOSED ERRATA | QA Contact: | Chao Ye <cye> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | urgent | ||||||
Version: | 6.9 | CC: | cww, cye, fkrska, goetz.waschk, ionut, jherrman, jsafrane, mkolaja, ondrej.valousek, ovasik, pkulkarn, varekova, weeksd2 | ||||
Target Milestone: | rc | Keywords: | Patch, Regression, ZStream | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | libcgroup-0.40.rc1-24.el6_9 | Doc Type: | Bug Fix | ||||
Doc Text: |
Previously, if the cgroup pluggable authentication module (PAM) was configured without arguments, the module terminated unexpectedly when opening the session. This update fixes argument processing so that such configuration is handled correctly, which prevents the described crash from occurring.
|
Story Points: | --- | ||||
Clone Of: | |||||||
: | 1494124 (view as bug list) | Environment: | |||||
Last Closed: | 2018-06-19 05:09:11 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: | 1374441, 1461138, 1494124 | ||||||
Attachments: |
|
Description
Nikola Forró
2017-02-06 12:01:15 UTC
Created attachment 1248024 [details]
Fixed libcgroup-0.40.rc1-reading-config-files-from-etc-cgconfig.d.patch
Simple workaround is to add an agrument to pam_cgroup.so (any string will prevent the crash, but only "debug" is actually recognized): session optional pam_cgroup.so debug The OS license might be $399 or whatever, but the fun of having to reboot a bunch of machines in single user mode to fix pam after applying this update is really priceless. You knew about this bug more than a month before the broken libcgroup got released in 6.9, and didn't do anything about it? Didn't mark it as a blocker? STILL didn't release a fix for it, 2 months after the busted release? That's just unconscionable. *** Bug 1465918 has been marked as a duplicate of this bug. *** @Ion: pam_libcgroup is from the optional channel, I take it RH does not provide the same support here. 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-2018:1861 |