Bug 1221766
| Summary: | ksh crashes under chroot environment with segmentation fault | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Yoshifumi Kinoshita <ykinoshi> | |
| Component: | ksh | Assignee: | Michal Hlavinka <mhlavink> | |
| Status: | CLOSED ERRATA | QA Contact: | Martin Kyral <mkyral> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 6.6 | CC: | asanders, clincoln, dkutalek, fkrska, jkejda, jkurik, jsvarova, mhlavink, ovasik, salmy, tbowling, wburrows | |
| Target Milestone: | rc | Keywords: | Patch, Reproducer, ZStream | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | ksh-20120801-29.el6 | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, the gcc utility optimized out a non-NULL test in the ksh implementation of the strdup() function. This caused an unexpected termination when ksh was executed in a clean chroot environment. With this update, ksh compilation parameters have been updated to prevent optimizing out a non-NULL test, and ksh no longer crashes in clean chroot environments.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1240942 1241556 1269088 (view as bug list) | Environment: | ||
| Last Closed: | 2016-05-11 00:46:04 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: | 1269088 | |||
| Bug Blocks: | 1172231, 1240942, 1241556 | |||
|
Comment 16
Terry Bowling
2015-06-26 16:31:31 UTC
(In reply to Terry Bowling from comment #16) > Could you submit these patches for review and change status of BZ to Post so that we can submit a formal accelerated fix request? That's what kernel engineering does, we don't. There is nothing missing/required 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://rhn.redhat.com/errata/RHBA-2016-0932.html |