Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 659289

Summary: kernel: additional stack guard patches [rhel-5.4.z]
Product: Red Hat Enterprise Linux 5 Reporter: RHEL Program Management <pm-rhel>
Component: kernelAssignee: Jiri Pirko <jpirko>
Status: CLOSED ERRATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: high    
Version: 5.6CC: cww, dhoward, eteo, fnadge, jarod, jpirko, jweiner, kzhang, lwang, lwoodman, plyons, pm-eus, rkhan
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: kernel-2.6.18-164.32.1.el5 Doc Type: Bug Fix
Doc Text:
1. Cause: Upward-growing mappings can expand into other mappings 2. Consequence: The consequences range from accidental corruption of the adjacent mapping to targetted overwriting of data in the adjacent mapping that otherwise would be impossible due to access protection 3. Fix: Prevent expansion from upward-growing mappings into adjacent mappings 4. Result: Expansion of an upward-growing mapping into an adjacent mapping will be caught and the responsible program be killed by sending it the SIGBUS signal
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-12 08:56:52 UTC Type: ---
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: 630563    
Bug Blocks:    

Description RHEL Program Management 2010-12-02 12:38:57 UTC
This bug has been copied from bug #630563 and has been proposed
to be backported to 5.4 z-stream (EUS).

Comment 3 Jiri Pirko 2010-12-16 15:08:28 UTC
in kernel-2.6.18-164.32.1.el5

linux-2.6-mm-add-guard-page-for-stacks-that-grow-upwards.patch

Comment 6 Florian Nadge 2011-01-04 12:18:23 UTC
Dear Jirko,

please add info on the bug to the field Technical Notes using the following
structure:

1. Cause:
2. Consequence:
3. Fix:
4. Result:

Many thanks,

Florian

Comment 7 Florian Nadge 2011-01-04 12:18:24 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
1. Cause:

2. Consequence:

3. Fix:

4. Result:

Comment 8 Florian Nadge 2011-01-04 12:23:03 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,7 +1,4 @@
 1. Cause:
-
 2. Consequence:
-
 3. Fix:
-
 4. Result:

Comment 11 Johannes Weiner 2011-01-04 14:56:06 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,4 +1,8 @@
 1. Cause:
+Upward-growing mappings can expand into other mappings
 2. Consequence:
+The consequences range from accidental corruption of the adjacent mapping to targetted overwriting of data in the adjacent mapping that otherwise would be impossible due to access protection
 3. Fix:
-4. Result:+Prevent expansion from upward-growing mappings into adjacent mappings
+4. Result:
+Expansion of an upward-growing mapping into an adjacent mapping will be caught and the responsible program be killed by sending it the SIGBUS signal

Comment 14 errata-xmlrpc 2011-01-12 08:56:52 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0015.html